Copyright: © Copyright 1997-2000 Alt-N Technologies


MDaemon Version 3

SMTP/POP/IMAP Server for Windows

Introduction

MDaemon Server v3 brings SMTP/POP/IMAP and MIME mail services commonplace on UNIX hosts and the Internet to a Windows based 486 or Pentium class microcomputer. MDaemon is designed to manage the email needs of any number of individual users and comes complete with a powerful set of integrated tools for managing mail accounts and message formats.

MDaemon Features

Some of MDaemon’s main features and capabilities in addition to SMTP/POP/IMAP:

•	MDaemon’s extensive parsing features make it possible to provide email for an entire LAN with as little as a single dial-up ISP POP3 mailbox. This makes it possible to provide email to an entire network for a fraction of the normally associated cost.

•	MDaemon Server v3 features a complete suite of Mailing List or email group management functions allowing for the formation of an unlimited number of distinct distribution lists that can contain local and/or remote members. Lists can be set to allow or refuse subscription requests, be public or private, post replies to either the list or the originator of the message, be sent in digest format, and be configured using numerous other features.

•	WorldClient Standard is now an integrated component of MDaemon. This exciting product makes it possible for your users to access their email using their favorite web browser rather than from a workstation dependent email client. This tool is perfect for mobile staff and users who do not have a dedicated machine from which to access their email.

•	The new Spam Blocker feature will help you put an end to most "spam" email messages that "spammers" try to route through or to your domain.

•	IP Screening and Suppression File functions provide the capability to screen and prevent certain addresses and domains from connecting to or sending mail through your system, as well as making it possible to connect to specific IP addresses while screening all others.

•	Address Aliases provides the ability to route to a valid account or mailing list email messages addressed to "fictitious" mailboxes. This makes it possible for individual accounts and lists to have "multiple" email addresses at one or more domains.

•	The Gateway Domain feature provides the option of setting up separate domains for various departments or groups that may be on a network. Using this feature, all mail addressed to a Gateway Domain would be placed in that domain’s mailbox from which it could be collected by another MDaemon and then distributed to that domain’s users.

•	Accounts can be controlled remotely by users by using specially formatted email messages. This allows greater administrative flexibility, and empowers users by turning day-to-day simple account maintenance tasks, such as changing passwords, over to them.

•	The new WebConfig feature enables your users to review and edit their account settings via their web-browser. You can designate which settings that your users may edit, and assign access permissions on a per account basis so that each user will only be able to edit those account settings you permit. This feature can also be used by the Administrator (and whomever  else you wish to allow) to review or edit any of MDaemon’s settings, and any other files that you wish to make available to the WebConfig system for reviewing from your browser.

•	Included with MDaemon is the MDConfig Remote Configuration Client. This utility makes it possible for a Network Administrator or Supervisor to access and change any of MDaemon’s settings from a remote location by easily installing it on a remote machine. Moreover, because its interface is virtually identical to MDaemon’s, you won’t have to familiarize yourself with a new set of controls.

•	With File Catalogs, the email administrator can create password protected groups of files which users can have encoded and automatically sent to them through the use of specially formatted email messages.

•	Account mailbox formats can be abstracted using Mailbox Format Files (MBF), which allows for a wide range of mail system compatibility.

•	An internal message transport system known as RAW mail provides a simple method for placing messages into the mail stream and greatly simplifies custom mail software development. Using RAW, a complete mail system can be devised using a simple text editor and a couple of batch files.

See:

What's New in MDaemon 3?

MDaemon's Main Display


What's New in MDaemon Version 3?

Information for those Upgrading from Previous Versions

MDaemon Version 3 incorporates many changes to its internal structure and many of its supporting DAT configuration files. Because of this change, the installation process automatically migrates your old v2.x configuration files to the new v3 formats where appropriate. Your old v2.x files are backed up and placed in the \OLDFILES\ directory during the installation process.

The addition of full multiple domain support has made it necessary to change several supporting DAT file formats including the USERLIST.DAT file. Consequently, version 3 is completely incompatible with the discontinued WebPOP series of products from Alt-N Technologies. WebPOP is no longer supported and will not be updated. Instead, we are providing our customers with our new WorldClient technology, which improves dramatically on the basic WebPOP idea.

There is no longer a POP logon field within the user database. Now, in keeping with a common industry standard, the Mailbox value is also used as the POP logon. If you have accounts that maintain different values for their Mailbox and POP logon, the conversion process, which is invoked automatically during installation, will change these account records to use the old logon value as the new mailbox. Then, aliases will be created for the new mailbox value in order to prevent your users from having to reconfigure their mail client or change their email address. Thus, their old Mailbox name will be an alias for their new Mailbox. The TRACKPOP.TXT file will list accounts that had to be updated in this manner. Further, in keeping with the removal of a stand-alone POP logon field, the $POPNAME$ macro has been discontinued. The conversion utility scans the appropriate .DAT files and removes this macro.

There is no longer a separate field in the user database for a \FILES\ directory. Now, an account’s \FILES\ directory will always be within its mail directory in a subdirectory called \FILES\. The conversion utility (automatically invoked during installation) adds entries to a file called TRACKDIR.TXT, which will detail any incompatibilities this might cause for any of your accounts. Additionally, there is no longer a separate \FILES\ directory for gateway domains. The \FILES\ subdirectory will always be maintained as part of the overall mail directory.

The aliasing system has been completely redesigned. Aliased accounts will be modified so go to the Address Aliases selection from the ‘Setup’ menu and carefully inspect your aliases as soon as possible.

WorldClient Standard 2, which ships free with this version of MDaemon, includes a new set of templates. WorldClient Standard 2 depends heavily on the format of these templates and the tags contained therein. Therefore, major template customization with WorldClient Standard is not possible.  To realize fully programmable, customizable templates, an upgrade to WorldClient Pro is required.

The documentation accompanying this installation is in Adobe Acrobat 4.0 format. If you wish to download documentation in MS Word 2000 format, you may do so via ftp://yoda.altn.com/MDaemon/md300word2000.zip.

See the Relnotes.txt file located in MDaemon’s \docs\ subdirectory for a complete list of all changes and fixes to MDaemon from previous versions.

Multiple Domain Support with Dedicated or Multi-homed IPs (Pro only)

MDaemon Pro now contains full support for multiple domains. In addition to MDaemon’s Primary Domain Configuration settings, it now contains a Secondary Domains dialog used for designating any number of additional domains that you want to support as well as the IP address to which each will be associated. MDaemon maintains local mailbox directories for all accounts within the primary and all secondary domains.  Therefore, it is no longer necessary to run multiple copies of MDaemon in order to service multiple domains in this fashion. As a consequence of this new capability, several controls and features such as User Accounts, Mailing Lists, and Security Settings are on a per domain basis rather than being global as in earlier versions.

For a complete discussion on Multiple Domain support and the interface changes resulting from this new feature, see:

Hosting Multiple Domains

Support for IMAP (Pro only)

MDaemon Pro supports the IMAP protocol. Now your users can take advantage of this more powerful mail access protocol when they use mail clients that support it. IMAP is similar to POP but is much more versatile. Because it allows server-based mail operations; users can store their messages and organize their mail folders on the server instead of their local machine, thus increasing the portability of their email access.

Spam Blocker

MDaemon v3 contains a new feature that can be used to prevent most "spam" email from reaching your users. This new security feature allows you to specify several ORBS/RBL type hosts (which maintain lists of servers known to relay "spam") that will be checked each time someone tries to send a message to your server. If the connecting IP has been blacklisted by any one of these hosts, the message(s) will be refused or flagged. See Spam Blocker for more information.

Account Manager Feature

To better manage the selection, addition, deletion, or modification of your accounts, an Account Manager has been added. This new interface provides much better access to account information and can be used to sort accounts by domain, name, or mail directory.

MDaemon/WorldClient Pro integration

MDaemon is now capable of seamlessly synchronizing user accounts with WorldClient Pro. When an account is created for a user within WorldClient, an identical account will be created for them in MDaemon, and the reverse is true as well. Additionally, WorldClient user sessions can be monitored from MDaemon’s main display, and MDaemon can be configured so that it and WorldClient will always be running at the same time. See MDaemon/WorldClient Pro Integration for further information.

Redesigned Aliasing Sub-system

The aliasing system has been completely redesigned. Rather than using a separate "alias the domain, alias the account" method that requires two separate editors, MDaemon now uses a single editor which aliases complete email addresses. See Address Aliases for more information.

Header Translation Feature

The "Outbound Domain Conversion" feature has been replaced with the Header Translation feature. This new dialog can change any portion of a message header’s text to a new value whenever a message is detected that must leave your domain and travel across the Internet. Header Translation is much more powerful and versatile than the old "Outbound Domain Conversion" feature while retaining the same basic functionality.

Improved Content Filter System

The Content Filter system has been improved and now supports AND/OR logic and more actions. This makes it possible to create much more complex rules for filtering your messages. Additionally, you may now use MDaemon’s macros (such as $Header:From$ or $Recipient$) to create rules that use dynamic data from the message itself rather than fixed data constants. See Content Filter for more information.

Message Precedence System

This new feature makes it possible for you to assign a "Precedence" value (level of importance) of 0 to 99 to messages. This value signifies the relative sort order of the messages during the delivery process. The lower the value, the higher its importance and the further up it will be in the sort order within a message queue. Thus, MDaemon will attempt to deliver a message with a value of 10 before one with a value of 90.

AUTH/POP before SMTP

As a security measure, many ISPs have begun to require their customers to perform a POP check, or in some other way authenticate themselves, before allowing them to send or receive mail through the ISP’s mail server. The AUTH/POP before SMTP feature has been added to make this possible for those from whom it is required.

See the Relnotes.txt file located in MDaemon’s \Docs\ subdirectory for a complete list of all changes and fixes to MDaemon from previous versions.


Installation

MDaemon Server v3 installs on any Microsoft Windows 9x/NT4/2000 computer system. SMTP/POP/IMAP and related services require a Winsock compliant TCP/IP stack, such as that which ships with Microsoft Windows, and a valid Internet hookup with an ISP service.

To install MDaemon Server v3 click Start|Run… and enter the path to the setup executable file provided in your MDaemon package, then click OK. Alternatively, you may install MDaemon by using "Add/Remove Programs" located in the Control Panel.

The installation process will prompt you for some basic information such as a registration name and a root directory where MDaemon files should be created. The installation process also provides a step-by-step configuration wizard that can be used to guide you through the most common configuration scenarios.

See:

Domain Configuration Editor
Account Defaults

See also:

DomainPOP Mail Collection


MDaemon's Main Display

Message Router

MDaemon’s Message Router automatically appears at program startup and gives you important information regarding MDaemon’s Resources, Statistics, Active Sessions, and Queued Mail waiting to be processed. It also contains controls for easily activating/deactivating MDaemon’s various servers. The Message and Event Tracking frame keeps you up to date on how the server and its incoming and outgoing connections are performing.

Statistics and Shortcuts Frame

The right frame of the Message Router contains three sections: Statistics, Queued Mail, and Servers. Click any of the controls in a section to select the given control and then right-click to open a shortcut menu relevant to that control.

The Statistics section contains statistics regarding the number of messages sent and received by MDaemon as well as the number of mail sessions that have been initiated since startup. This section also tells you how many user accounts have been used and how many more can be created. Statistics contains two shortcut menus: one for the Accounts controls and one for the Statistics controls. The Accounts shortcut menu provides shortcuts for creating, editing, and deleting accounts. The rest of the controls have a shortcut menu that can be used to reset to zero the count listed next to the given control.

The Queued Mail section contains an entry for each message queue, and the number of messages (if any) that each queue contains. Each control’s shortcut menu can be used to process the queue and to open the Queue and Statistics Manager, which can be used for viewing, copying, or deleted the contents of the queue, as well as a number of other functions.

The Servers section contains an entry for each server within MDaemon, and each entry lists the current state of the server: "Active" or "Inactive". Listed below each entry is the port on which that particular server is listening, if that server is currently active. The shortcut menu provides a control for toggling each server between the Active and Inactive state.

Message and Event Tracking Frame

The left frame of the Router displays the status of the server, and is frequently updated to reflect current server conditions. Each SMTP/POP/IMAP session is logged into this frame once it is complete so that a permanent record of network activity is made available.  The information contained in this window is mirrored in the log file kept in the Logs directory.  At program startup, this window displays a log of the Initialization Process, which can alert you to possible problems with MDaemon’s configuration or status.

Session Monitor Frame

The bottom frame of the display is for monitoring active sessions. The session monitor contains information and statistics regarding active SMTP/POP/IMAP sessions, as well as WorldClient session statistics for each user that is logged into WorldClient.

Note
The layout of the panes in the Message Router window is not limited to the default positions described above. You may change the layout be selecting the Windows menu selection and then clicking the Switch panes control corresponding to the desired layout.

See:

Connection Window


Connection Window

A Connection Window appears each time a request is detected by the server from some remote client, or whenever a session is initiated by the server to collect or deliver a message. This window keeps you informed of the status of the transaction and alerts you to any problems encountered during the course of the mail session.

Session transcript

This window displays all session i/o.

Remote host/IP

This window tells you the name and IP address of the remote computer MDaemon with which MDaemon is interacting.

Message from/to

This window displays the sender’s address and the address of the intended recipients.

Message transfer statistics

This keeps a running total of the number of bytes transmitted to or collected from the remote system, the percentage completed, and the current speed of the transfer.

Inactivity timeout

This counter displays how much inactivity time is left before MDaemon will close the session.

Disconnect

This button will immediately disconnect the server from the remote system.


Domain Configuration Editor

The domain configuration editor can be reached via the SETUP | PRIMARY DOMAIN menu selection and allows you to enter several key pieces of information regarding your domain setup. Your primary domain is the default domain name and set of configuration options that your users will use to send and receive their email. This is also the domain that will be used when you are utilizing the MDaemon/WorldClient Pro Integration feature to automatically create WorldClient accounts. Only one primary domain can be configured, but MDaemon can manage mail for any number of Secondary Domains, and store mail for any number of Gateway Domains as well.

The Domain Configuration editor is a tabbed dialog containing the following sections, which are necessary for configuring MDaemon v3.

Domain/ISP

This dialog contains your Primary Domain’s name and IP address. In addition, here you will specify the degree to which you want MDaemon itself to handle delivery of mail versus relaying mail to an ISP or gateway host for them to deliver for you.

Pre-Processing

This dialog is used to designate the path to any program that you may want MDaemon to run immediately before processing and delivering of mail. Here you can also set parameters for MDaemon’s actions related to this process.

Dequeue

Use the Dequeue tab to have MDaemon automatically send ETRN, QSND, or similar commands to an ISP in order to have them dequeue email that you may have them "holding" for you so that you can receive this sort of email via SMTP rather than DomainPOP.

Directories

Here you can specify paths to the locations of various directories that MDaemon will use for Remote and Local queues, work files, archiving, Mailing List Digest files, and so on.

Archival

Use the Archival tab to save a copy of all inbound and outbound mail that MDaemon processes. You can also choose whether this archive will include Mailing List or MultiPOP messages or omit them.

Ports

On this dialog, the ports that MDaemon will monitor and use for SMTP and POP email delivery are designated. You will also designate the port on which MDaemon will listen for IMAP events, and the UDP port used for querying DNS servers. In most cases the default settings will not need to be changed. However, being able to configure these port settings is useful when attempting to integrate MDaemon with various other products that you may be using on your system.

DNS

This dialog is used for designating a primary and backup DNS server’s IP address. It also contains various controls governing MDaemon’s handling of MX and A records and SMTP errors that are encountered during mail delivery.

Timers

This area contains various time limits that MDaemon will observe while connecting to remote hosts, waiting for protocol dialogs, waiting for DNS server responses, and so on. In addition, this dialog contains the Maximum Message Hop Count limit, which is used to help prevent messages from being caught in a delivery loop.

Threads

Here you will designate the maximum number of concurrent session threads that MDaemon will use for sending and receiving SMTP, POP, and IMAP mail. You will also designate the number of messages that MDaemon will attempt to send/receive at the same time.  In addition, if you so choose, you can set a limit on the number of outbound SMTP messages that will be spooled per session thread.  Further, if you are using the Mailing List features, you can designate whether you want MDaemon to continue processing sessions while "cracking" mailing list messages that may arrive at the server.

Unknown Local Mail

This dialog contains various settings that you can use to control what MDaemon will do with messages that arrive at the server addressed to a Local domain but to an unknown or undefined user’s mailbox. The various control choices include: sending the email message back to the sender, sending it to the Postmaster, putting it in the Bad Message queue, and forwarding the message to another host. These controls may be set to act individually or in any combination.

See:

Hosting Multiple Domains

Secondary Domain Editor

Gateway Domains

See Also:

MDaemon/WorldClient Integration

DomainPOP Mail Collection


 Domain/ISP

Primary Domain Properties

Domain name

Enter your primary domain name here. This is the default domain name used when creating new accounts. It is also used in the WorldClient accounts that are created automatically when you are utilizing the MDaemon/WorldClient Pro Integration features. Typically, the value entered here will be the registered Internet domain name that a DNS server resolves to the IP address of the local machine running the server, or a qualified alias of that name.

Alternatively, you may choose to use a fictitious domain name for your Primary Domain Name (such as "company.mail") in some situations.  When configuring your server in this way it may be necessary to use the Header Translation feature, and/or the Domain Name Replacement Engine, to enable proper mail distribution.

HELO domain

This Domain name will be used in the SMTP HELO/EHLO instruction when sending mail. In most cases, this will be your Primary Domain Name.

Domain IP

This is the Primary Domain’s IP address.

Bind listening sockets to this IP only

Selecting this switch causes MDaemon to bind its listening network sockets using the specific IP address found in the Domain IP text box.  Ordinarily, this control will only need to be used in certain circumstances when hosting multiple domains.

For more information on this type of configuration, see:

Hosting Multiple Domains

ISP or Gateway Host Properties

ISP/gateway host’s IP or domain name

Specify your mail gateway’s host name or IP address here.  This is generally the SMTP server on your ISP.

Note
Do not enter one of your local Domains or IP addresses into this text box. This entry should be an Internet gateway host other than yourself that can relay mail for you.

Send every outbound email message to the gateway host

Select this option if you want all outbound email, regardless of its destination domain, to be spooled to a gateway host for routed delivery. If selected, all outbound email will be sent to the host specified in the Gateway Host’s IP or Domain Name field. Typically, this feature is useful during high volume periods when direct message delivery would result in an excessive taxation of server resources.

Send only undeliverable outbound mail to this host

Click this option if you want to spool only undeliverable outbound email to the gateway host specified in the ISP/gateway host’s IP or domain name field. Undeliverable mail is email destined for hosts that could not be resolved to an actual IP address (such as an unregistered gateway to a remote network) or email destined for a host that was resolved properly but could not be connected to directly or is refusing direct connections. Rather than return such mail to its originator, this option causes MDaemon to pass the message off to a more powerful MTA. Sometimes the mail system run by your ISP may have routed methods of mail delivery to which your local server may not have direct access.

Attempt to send all mail direct without using an intermediate host

When this option is chosen, MDaemon will attempt to deliver all mail itself instead of passing it to another host. MDaemon will place undeliverable messages into its Retry System and continue to attempt to deliver them according to the parameters and time intervals that you set in the Retry Configuration dialog. You can access this dialog by clicking the Retry Queue Settings button.

My ISP requires me to log in before sending mail

As a security measure, in order to prevent unauthorized users from attempting to relay mail through their servers, some ISPs require their customers to authenticate themselves via ESMTP AUTH or by first performing a POP check of their email account. If this is the case for your ISP, you can open the AUTH/POP before SMTP dialog by clicking this button. There you can enter the required authentication information.

Retry queue settings

Click this button to open the Retry Configuration dialog from which you can designate how often MDaemon will attempt to deliver messages which it has thus far been unable to deliver. You can also specify a time interval after which the attempts will cease, and what to do with these messages after the final attempt is made.


Retry Queue Settings

Retry Frequency

Keep message in the primary queue for at least xx minutes

This setting governs the length of time a message will remain in the primary queue before being removed and placed in the retry queue.  The primary queue will generally attempt to deliver the message quicker and more frequently than the retry queue.

Retry sending undeliverable mail once every xx minutes

This setting determines how frequently the messages in the retry queue are processed.

Inform the sender when message is placed in retry queue

This switch will inform the sender when his/her message is removed and placed in the retry queue.  The text of this message can be found (and edited) in the DELWARN.DAT file.

Inform the sender when subsequent delivery attempts fail

If a delivery attempt of a message in the retry queue fails, a message explaining this fact will be dispatched to the sender of the message.  The text of this message can be found (and edited) in the DELWARN.DAT file.

Ultimate Fate of Undeliverable Mail

If a message is still undeliverable after xx days then:

This setting determines the number of days that a message can remain in the retry queue before being removed.

Place the undeliverable message in the bad message queue

Once a message has reached the time limit set in the If A Message Is Still Undeliverable After xx Days Then: control, a copy of that message will be moved to the bad message directory if this switch is enabled.

Inform the sender that the message could not be delivered

Once a message has reached the time limit set in the If A Message Is Still Undeliverable After xx Days Then: control, this switch will cause MDaemon to send a message to the sender informing them that the message has been permanently removed from the server. The text of this message can be found (and edited) in the DELERR.DAT file.

Inform the postmaster that the message could not be delivered

If this switch is enabled, the postmaster will be notified when a message has been permanently removed from the retry system.

. . . unless it’s an mdaemon auto-generated message

The retry system will never inform MDaemon when an auto-generated message fails to be delivered. However, because such information may be useful to the postmaster, he or she will be informed when these messages cannot be delivered. Click this checkbox if you do not want the postmaster to be informed when auto-generated messages cannot be delivered. Examples of auto-generated messages are return-receipt notifications, auto-responder generated messages, results of account processing, and so on.


 Pre-Processing

Local/Remote Queue Pre-Processing

Just before processing the (local/remote) mail queue run this program

This field specifies a program path and name that will be executed just prior to the processing and delivery of any RFC-822 messages that might be in the local or remote message queues. If complete path information is not provided, MDaemon will first search for the executable in the MDaemon directory, then in the Windows System directory, next in the Windows directory, and finally the directories listed in the PATH environment variable.

…suspend all operations for xx seconds

The value entered here determines how MDaemon will behave while the specified program is in progress. MDaemon can be configured to pause its execution thread for the number of seconds specified while waiting for the process thread to return. If the process returns before the number of seconds has elapsed, MDaemon will resume its execution thread immediately. Enter the numeral zero in this control and MDaemon will not suspend operations at all. Entering "-1" will cause MDaemon to wait until the process returns, no matter how long that might be.

Don’t execute when queue is empty

Enable this switch if you do not want the specified program to run when the queue is empty.

Force process to terminate

Sometimes the process you need to run may not terminate on its own. This switch will cause MDaemon to force the session to terminate once the time specified in …Suspend All Operations For XX Seconds has elapsed. This switch does not work if the elapsed time interval is set to "-1".

Run process in a hidden window

Click this checkbox if you want the process to run in a hidden window.


 Dequeue

Dequeue Engine

Signal ISP to dequeue waiting mail

When it is time to process remote mail MDaemon can connect to any server on any port and send any string that you wish to send. This is useful when you need to signal a remote server to release your mail by sending some string to them. For example, ATRN, ETRN, or QSND. You can also use this feature when a FINGER or TELNET session is briefly required in order for your ISP to determine that you are online.

Send signal once every [xx] times remote mail is processed

By default the dequeue signal will be sent each time that remote mail is processed. Entering a number into this control will prevent the dequeue signal from being sent every time. It will be sent every x number of times as designated. For example, setting this value to "3" would cause the signal to be sent every third time that remote mail is processed.

Remote Server

Send signal to this remote host

This is the host to which you wish to connect to signal the release of your mail.

Use this TCP port

Enter the port on which you wish to make the connection. The default is 25 (the SMTP port), which is appropriate for the ETRN or QSND signaling method. Port 366 is typically used for ATRN, and port 79 is used for FINGER.

Dequeue Instruction

Send this string to host

This control is for specifying the text string that needs to be sent in order for your mail to be released. For example, the ETRN method requires the text "ETRN" followed by the domain name of the site being queued. Other methods require different text to be sent.  Consult your ISP if you need more information on what to send to unlock your mail queue.

Note
When using a dequeue method of mail hosting, we recommend using On-Domain Mail Relay (ODMR) whenever possible. We believe that it is currently the best method available for hosting your email in this manner. ODMR requires the ATRN command to be used in this control.

Send SMTP "HELO" before transmitting string to host

If you enable this checkbox then you should be connecting to an SMTP server to signal release of your mail. This switch causes an SMTP session to be initiated with the specified host and allows the session to progress just beyond the SMTP "EHLO" stage before sending the unlock string.

I must authenticate before sending the dequeue signal (required for ATRN)

As a security measure, in order to prevent unauthorized users from attempting to dequeue their customers email, some ISPs require their customers to authenticate themselves via ESMTP AUTH before sending the dequeue signal. If this is the case for your ISP, you can open the Dequeue AUTH dialog by clicking this button. There you can enter the required authentication information.

Note
Authentication is required when using the ATRN command to dequeue your email.

Session Windows

Hide dequeue session windows while they are in progress

Click this checkbox if you want to hide sessions windows while they are in progress.

Note
If the value you enter into the Send Signal To This Host control is a domain name and not an IP address, MDaemon will perform an MX record resolution of this site in an attempt to connect to the site’s MX IP address. This assumes you have the MX resolution engine switched on and working (see DNS). If the value entered is an IP address and not a domain name then the connection will be made using that IP address.

On-Demand Mail Relay (ODMR)

We believe that the best relay (queue/dequeue) method currently available for hosting your email is On-Demand Mail Relay (ODMR). This method is superior to ETRN and other methods in that in requires authentication before mail is dequeued. Further, it utilizes a new ESMTP command called ATRN that does not require the client (customer) to have a static IP address because it immediately reverses the flow of data between the client and server (provider) and despools the messages without having to make a new connection to do so (unlike ETRN).

MDaemon fully supports ODMR on the client side via using the ATRN command and authentication controls on the Dequeue tab, and on the server side using the Gateway Domain features on the ATRN / AUTH tab of the Gateway Domains Editor.

Many mail servers do not yet support ODMR therefore you should check with your provider before attempting to use it.


 Directories

Directories

RAW formatted mail is picked up from this directory

Enter the directory path where MDaemon Server v3 should expect to find RAW format messages that are to be processed and entered into the mail stream. This directory is scanned at each local mail processing interval for RAW mail, which the server then converts to RFC-822 and delivers to its intended recipient(s).

For a complete discussion of RAW message specifications see:

RAW Message Specifications

Bad messages (parsing errors, unknown  users, etc) are placed here

Enter the directory path where bad messages should be placed. The bad message queue will contain messages destined for unknown yet supposedly local users, and messages that cause parsing problems.

When Collecting Inbound Mail, Work Files Should Be Stored Here

Enter the directory path where MDaemon should store incoming transient SMTP mail messages. This work directory is used only while an SMTP session is in progress. While a session is ongoing, the messages being delivered to the server are stored in temporary files in this directory.

RFC-822 compliant remote message queue (non-local mail only)

Enter the directory path that MDaemon should use as the outbound mail queue. This directory will contain only processed RFC-822 format messages that are waiting for delivery to their final destination or to the mail gateway. All mail placed in this directory must be RFC-822 compliant and have an extension of MSG in order to be processed by MDaemon. Mail in this queue is destined for domains hosted by other servers.

RFC-822 compliant local message queue (local mail only)

Enter the directory path that MDaemon should use as the local mail queue. This directory will contain only processed RFC-822 format messages that are waiting for delivery to their final destination or to a mail gateway. All mail placed in this directory must be RFC-822 compliant and have an extension of MSG in order to be processed by MDaemon. Mail in this queue is destined for local mailboxes.

If you are using the LAN Domains feature, messages destined for other servers on your local LAN will be stored in a subdirectory of the this Local Message Queue called Lndomain.

See:

LAN Domains

Mailing list digests are stored here while waiting to be queued

Enter the directory path where MDaemon should store Digest mail waiting to be queued for delivery.

Mailing list digests are archived here

Enter the directory path where MDaemon should Archive Digests.

Log transcript files are stored here

Enter the directory where transaction and event logs are stored.


 Archival

Archive Settings

Archive a copy of all inbound/outbound mail

This switch enables the archival engine. Activating it will cause a copy of every inbound and outbound message that passes through the server to be sent to the address(es) specified in the control following.

Send a copy of every inbound/outbound message to these addresses

Enter one or more addresses to which you wish to send archival messages. Multiple addresses must be separated by a comma. You may specify Local and Remote addresses and Address Aliases.

Include mdaemon mailing list messages in the archive also

Select this switch if you want archived mail to include your mailing list messages.

Include MultiPOP collected mail in the archive also

Select this switch if you want archived mail to include messages collected through MDaemon’s MultiPOP feature.

Label archive messages with "(archive copy)" in message subject

Enable this switch if you want to include "(Archive Copy)" in the Subject: header of archived mail.

Note
Archival copies of message will not be processed through the content filtering system


 Ports

SMTP/ODMR Server Ports

Listen for inbound SMTP events on this TCP port

MDaemon will monitor this port for incoming connections from SMTP clients.

Create outbound SMTP events using this TCP port

This port will be used when mail is sent to other SMTP servers.

Listen for inbound ODMR events using this TCP port

MDaemon will monitor this port for incoming On-Demand Mail Relay (ODMR) connections such as ATRN from Gateway Domains.

POP/IMAP Server Port Settings (IMAP Available in MDaemon Pro only)

Listen for inbound POP3 events on this TCP port

MDaemon will monitor this port for incoming connections from remote POP clients.

Create outbound POP3 events using this TCP port

This port will be used when mail is retrieved from POP3 servers.

Listen for inbound IMAP events on this TCP port

MDaemon will monitor this port for incoming IMAP requests.

DNS Server Port Settings

Query DNS servers using this UDP port

Enter the Port you want MDaemon to use for sending and receiving data grams to the DNS server.

LDAP port for database & address book posting

MDaemon will post database and address book information to your LDAP server on this port.

See: LDAP Address Book Support

Remote Configuration Server Port Settings

Listen for MDConfig connections on this TCP port

This is the port that MDaemon will monitor for MDConfig connections.

Listen for WebConfig connections on this TCP port

This is the port that MDaemon will monitor for WebConfig connections.

Return port settings to defaults

This button returns all the port settings to their standard values.

Bind to new port values now

When you alter the values of any of the port settings you will need to press this button to have your changes take immediate effect. Otherwise, your changes will not be put into place until the next time the server is started.

Note
The preceding port settings are critical for proper server operation and should not be altered unless you are certain that you must do so. Being able to configure the ports that MDaemon uses will allow you to configure the server to operate with proxy systems or other software services that require certain port numbers.

An IP address (a machine) has only one of each available port. If another program attempts to gain access to a port that is already in use by another piece of software an error message will inform the user that the requested address (IP:PORT) is already in use.


 DNS

DNS Server Settings

Try to use DNS servers defined in Windows TCP/IP settings

Windows sometimes keeps a DNS server IP address in the local TCP/IP configuration. If this is the case on your computer then you can check this option. If MDaemon cannot find a locally maintained DNS server it will continue on and use the ones specified on this screen.

Primary DNS server IP address

Enter the IP address of the DNS server that you want MDaemon to query for ‘A’ and ‘MX’ records. In order to ensure proper operation this entry must be specified.

Backup DNS server IP address

Enter the IP address of the backup or secondary DNS server that you want MDaemon to query for ‘A’ and ‘MX’ records. This entry is optional but recommended.

Retry failed lookup attempts this many times

If for some reason a lookup attempt fails, this is the number of times that MDaemon will repeat the attempt. If you have designated a backup DNS server, both servers will be included in each lookup attempt.

MX Record Processing

Query DNS servers for MX records when delivering mail

Enable this control if you want MDaemon to query your designated DNS servers for ‘MX’ records when it is attempting to deliver mail.

Use ‘A’ record IP addresses found within MX record packets

Click this checkbox if you want MDaemon to attempt delivery to ‘A’ record IP addresses when such are discovered during ‘MX’ record processing.

Send message to next MX host when an SMTP error occurs

With this function active, MDaemon will continue to attempt message delivery to the next ‘MX’ hosts even if the current ‘MX’ returns a fatal SMTP error.

Immediately return mail when DNS says domain does not exists

This switch will cause MDaemon to immediately return a message if a DNS lookup returns a "Domain Does Not Exist" message.  This will prevent this sort of mail from needlessly going into the delivery retry cycle.

Local Lookup Tables

Hosts file…

Before querying the DNS servers, MDaemon will first attempt to resolve an address by processing the Windows HOSTS file. If this file contains the IP address of the domain in question, MDaemon will not need to query the DNS server.

Note
You must enter the complete path and filename rather than just the filename.  MDaemon will attempt to use the following values as the default location of this file:

Windows 95/98 - [drive]:\windows\hosts
Windows NT - [drive]:\windows\system32\drivers\etc\hosts

The HOSTS file is a Windows file that contains the A-record or primary IP address for a domain name. MDaemon also allows you to specify MX-record IP addresses within a file called MXCACHE.DAT. This file can be found within the MDaemon\APP\ subdirectory. Load the MXCACHE.DAT file into a text editor and read the comments at the top of the file for more information.

Edit MXCACHE file

Click this button to view or edit the MXCACHE.DAT file with MDaemon’s text editor.

Edit hosts file

Click this button to view or edit the HOSTS file with MDaemon’s text editor.


 Timers

Event Timers (IMAP options available in Pro version only)

Wait xx seconds for sockets to connect before giving up

After initiating a connection request MDaemon will wait this many seconds for the remote system to accept the connection. If the remote system does not respond within this time frame MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.

Wait xx seconds for protocol dialog to start before giving up

Once a connection has been established with a remote host, this is the number of seconds that MDaemon will wait for the remote host to begin the SMTP or POP3 protocol dialog.  If the remote host does not begin the protocol session within this time frame MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.

Wait XX seconds for MX DNS server responses

While using DNS services to resolve ‘MX’ hosts for remote domains, MDaemon will wait for responses to its ‘MX’ queries for this number of seconds. If the DNS server does not respond within this time frame MDaemon will attempt to deliver the message to the IP address specified in the remote host’s ‘A’ DNS record. If that attempt fails MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.

Wait XX seconds for A-Record DNS server responses

This timer governs how long MDaemon will wait while attempting to resolve a remote host’s IP address. If the attempt fails, MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.

SMTP and POP sessions timeout after XX inactive minutes

If a successfully connected and operating session remains inactive (no i/o) for this length of time, MDaemon will abort the transaction. MDaemon will try again at the next scheduled processing interval.

IMAP sessions timeout after xx inactive minutes

If an IMAP session has no activity for this number of minutes, MDaemon will close the session.

IMAP NOOP commands trigger 1 minute inactivity timeout

When this checkbox is enabled, the IMAP inactivity timer will be set to one minute when a NOOP command is encountered. Some IMAP clients will issue NOOP commands simply to keep sessions open even though there is no actual mail transaction activity going on. This feature will prevent such sessions from remaining active and thus will reduce resources consumed, which can be extremely useful for higher volume IMAP based mail sites.

Loop Detection and Control

Maximum message hop count (1-100)

RFC standards stipulate that a mail server must stamp each message each time that it is processed. These stamps can be counted and used as a stopgap measure against recursive mail loops that can sometimes be caused by errant configurations. If undetected, these looping message delivery cycles will consume your resources. By counting the number times the message has been processed, such messages can be detected and placed in the bad message directory. The assumption is that if a message hasn’t reached its recipient after being processed by a given number of mail servers then there is probably a mail loop in progress. Most likely, the default setting of this control should be sufficient to prevent mail loops and will not need to be changed.

Latency

Latency – xx milliseconds

This is the delay in milliseconds between POP/SMTP/IMAP protocol commands. This is useful for preventing high-speed connections from processing data faster than the recipient can extract it. This delay takes effect only during the POP/SMTP/IMAP protocol command sequence – the actual transfer of a mail message file is already fully buffered.


 Threads

SMTP

Maximum concurrent SMTP outbound session threads

The value entered here represents the maximum possible outbound SMTP session threads that will be created when it is time to send outbound mail. Each session thread will send outbound messages until either the queue is empty or the Max SMTP Outbound Messages Spooled Per Thread setting has been reached. For example, if the outbound mail queue has twenty messages waiting when it is time to send mail and the value of this setting is five, then five session threads will be simultaneously created and each will consecutively deliver four messages.

You should experiment with the number of session threads that yield the best performance for your bandwidth.  It is possible to specify so many threads that your bandwidth will be overloaded or your Windows machine will run out of resources and you will lose delivery efficiency. Remember, each SMTP session thread created by MDaemon will deliver messages consecutively and therefore four threads delivering two messages each might perform better and faster than eight threads delivering only one message each. A good place to start would be five to ten threads when using a 28.8k modem and ten to fifteen for ISDN.

Maximum SMTP outbound messages spooled per thread

This setting places a limit on the number of individual messages that each session thread will send before it stops delivering mail and frees itself from memory. Ordinarily, you should leave this control set to zero, which will cause each session thread to continue delivering messages until the queue is empty.

Maximum concurrent SMTP inbound session threads

This value controls the number of concurrent inbound SMTP sessions threads that the server will accept before it begins responding with a "Server Too Busy" message.

Enable SMTP expansion threading

When this setting is enabled, MDaemon will continue processing other sessions while cracking large mailing list messages that arrive via SMTP.

POP/IMAP (IMAP options available in Pro version only)

Maximum concurrent POP outbound session threads

The value entered here represents the maximum possible outbound POP session threads that will be created when it is time to collect DomainPOP and MultiPOP mail. Each session will collect this type of mail until all DomainPOP and MultiPOP servers have been processed, and all mail has been collected. For example, if there are fifteen MultiPOP sessions amongst all of your users and the value of this setting is set to three, then each session thread will collect mail from five MultiPOP sources.

You should experiment with the number of session threads to determine what number will yield the best performance for your bandwidth. It is possible to specify so many threads that your bandwidth will be overloaded, or your Windows machine will run out of resources and you will lose processing efficiency. Remember that each POP session thread created by MDaemon will collect mail until all sources have been exhausted. Therefore, four threads collecting mail from twenty sources might perform better and faster than twenty threads collecting from a single source. A good place to start would be two to five threads with a 28.8 modem and five to ten for ISDN.

Maximum concurrent POP/IMAP inbound session threads

This value controls the maximum number of concurrent POP and IMAP inbound mail sessions that the server will accept before it begins responding with a "Server Too Busy" message.

Enable POP3 expansion threading

When this setting is enabled, MDaemon will continue processing other sessions while cracking large mailing list messages that arrive via DomainPOP.


 Unknown Local Mail

What To Do With Mail For Unknown Local Users

Route message back to sender

Messages that arrive at the server destined for unknown yet supposedly local users will be returned to the message originator if this option is activated.

Send message to the "postmaster" user

Messages that arrive at the server destined for unknown yet supposedly local users will be forwarded to whatever user has been aliased as the postmaster.

Place message in bad message directory

Messages that arrive at the server destined for unknown yet supposedly local users will be routed to the bad message directory.

Advanced Options

Enable advanced options

Click this checkbox to enable the following advanced mail routing properties.

Send the message to this host

If a mail host is specified here, messages addressed to unknown local users will be sent to it.

Use this address in SMTP envelope

This address will be used in the SMTP "Mail From:" statement used during the session handshaking with the accepting host. Normally the sender of the message is used in this portion of the SMTP envelope. If you require an empty command (MAIL FROM <>) then enter "[trash]" into this control.

Use this TCP port

MDaemon will send this message on the TCP port specified here rather than the default SMTP outbound port.


Hosting Multiple Domains (MDaemon Pro only)

MDaemon Server Version 3 contains full support for multiple domains. In addition to the Primary Domain Configuration settings, it now contains the Secondary Domain Editor used for designating any number of additional domains that you want to support as well as the IP address to which each will be associated. MDaemon supports both dedicated and multi-homed IP addresses.

MDaemon supports multi-homing or sharing the same IP across multiple different domains. To achieve this MDaemon automatically detects the IP address that an incoming connection is attempting to reach and will use the appropriate domain name accordingly. For example, suppose you have the following domains and accounts configured:

altn.com, IP = 1.1.1.1
user-1@altn.com, logon = user-1, POP password = ALTN

arvelh.com - 2.2.2.2
user-2@arvelh.com, logon = user-2, POP password = ARVELH

If a connection is attempted to 1.1.1.1 then MDaemon will answer as "altn.com". If a connection is made to 2.2.2.2 then "arvelh.com" will be used.

If user-1@altn.com connects to 1.1.1.1 to check his mailbox, he will supply "user-1" as his logon and "ALTN" as his password to logon. However, if user-2@arvelh.com connects to 1.1.1.1 to check his mail then he is technically connecting to the wrong server (he should be connecting to 2.2.2.2). In that case, he will need to supply his full email address in the logon field to gain access. Of course, if he had connected to 2.2.2.2 he would only need to supply his logon value. Therefore, if an account connects to the IP address corresponding to its domain, and that IP address is not used by any other domain, then the account need only specify the logon value. Otherwise, it must specify a complete email address. In this way, support for servicing multiple domains can be accomplished using a single IP address. When several domains share the same IP address then the logon must contain the full email address. Otherwise MDaemon will not know which user is attempting to logon. When in doubt use the full email address as your logon value.

So, how is the logon and domain specified? You would expect that providing the account’s email address would work like this: arvel@altn.com. However, it turns out that many email clients on the market today will not allow the ‘@’ symbol to be used in the logon field. MDaemon will always accept logon values which contain the ‘@’ symbol, so if your mail client supports using the ‘@’ symbol in the logon value you are home free. To accommodate those mail clients that do not permit this, MDaemon allows you to specify an alternative character. MDaemon’s default alternative character is ‘$’. That means that you could use: arvel$altn.com as easily as arvel@altn.com. You can configure the delimiter character that you want to use by editing the following key inside the MDaemon.ini file:

[Special]
POPDelimiterChar=XXXX

This value can be up to 10 chars long, making it possible to provide a string of characters that serve as the delimiter. For example, using .at. will allow you to make logon values of "arvel.at.altn.com".

Several key features, such as Accounts, Mailing Lists, and Security Settings, are on a per domain basis. When you create a mail account you must specify the domain to which the new account belongs. The same goes for Mailing Lists. This means that features such as the IP Screen and IP Shield are tied to domains individually. Although some features, such as the DomainPOP ‘Real Name Matching’ feature, are tied exclusively to the primary domain.

As part of the multi-domain process, when you create a secondary domain the following aliases will be setup to automatically:

MDaemon@secondarydomain.com = MDaemon@primarydomain.com

listserv@secondarydomain.com = MDaemon@primarydomain.com

listserver@secondarydomain.com = MDaemon@primarydomain.com

list-serv@secondarydomain.com = MDaemon@primarydomain.com

These aliases will be automatically removed if the secondary domain is deleted.


Secondary Domain Editor

MDaemon Server Version 3 contains full support for multiple domains. In addition to the Primary Domain Configuration settings, it now contains the Secondary Domains Editor used for designating any number of additional domains that you wish to support as well as the IP address to which each will be associated. MDaemon supports both dedicated (static) and multi-homed IP addresses.

On the Secondary Domains Editor, for each secondary domain that you wish to host, you will include: the domain name, the IP address to which it will be associated, and whether or not it will be bound to its IP address.

Adding a Secondary Domain

To add a secondary domain to the Domain List:

1.	Enter the Domain Name and IP Address.

2.	Click Bind To This IP (only if you want to bind the domain to its IP address).

3.	Click Add.

Editing a Secondary Domain

To edit a secondary domain:

1.	Click the Domain List entry that you wish to edit.

2.	Make any desired changes to the information the will appear in the controls.

3.	Click Replace.

Removing a Secondary Domain

To remove a secondary domain:

1.	Click the entry that you wish to remove from the Domain List.

2.	Click Remove.

For more information on hosting multiple domains, see:

Hosting Multiple Domains

See also:

Primary Domain Configuration
Account Editor

Secondary Domains

Domain List

This window contains the list of your secondary domains. This list has three columns: Domain Name—which lists the name of the each domain, IP—each domain’s IP address, and Bind—which shows whether or not the given domain is bound to its IP address. This list can be sorted in ascending or descending order by any column. Simply click the column by which you wish to sort the list and it will be sorted by that column in ascending order. Click the same column again to sort it in descending order.

Domain name

Enter the domain name of the secondary domain that you wish to host.

IP address

Enter the IP address to associate with the domain being added or edited.

Bind to this IP

Click this checkbox if you want to bind the secondary domain to its IP address.

Add

Click this button to add the secondary domain along with its IP address and binding status to the Domain List.

Replace

When you click an entry in the Domain List, its settings will appear in the corresponding controls. Click this button after making any desired changes to the information to replace the entry with the new settings.

Remove

After selecting an entry in the Domain List, click this button to remove it from the list.


Setting up Remote Configuration

Use the Setup|Remote Configuration… menu selection to setup access to your server from the MDConfig remote configuration client, or from the browser-based WebConfig server. By using these features you can review or edit any of MDaemon’s controls or settings from a remote location.

The Remote Configuration dialog is used to designate whether or not MDaemon will allow remote configuration from MDConfig, WebConfig, or both, and on which ports it will connect to these utilities. In addition, you may assign separate login and password values for both Administrator and Supervisor access from MDConfig, and you may designate specific IP addresses from which it will be permitted to connect to MDaemon. This effectively makes it possible to permit remote configuration access from only specific machines. Lastly, you may specify a directory in which MDaemon will place a backup of its existing configuration files before it updates any changes that you may have made.

For more information regarding MDConfig and WebConfig, see:

MDConfig Remote Configuration Client

WebConfig Remote Configuration Server

Web Access Defaults

Account Editor|Web

Remote Configuration

Remote Configuration Engines

Enable MDConfig remote configuration engine

Click this Checkbox to enable support for remote configuration. MDaemon will listen for connections on the MDConfig port specified on the Domain Configuration Editor (page 35). With this switch turned off, all attempts to remotely configure the server using MDConfig will fail. The MDConfig server can also be enabled/disabled from the Message Router.

Enable WebConfig remote configuration using port [XX]

Enable this checkbox if you want to enable MDaemon’s WebConfig server. With this server active, MDaemon’s files can be edited through the use of a web browser by connecting to MDaemon’s primary domain URL and specifying the port on which WebConfig is listening (page 35). For example: if your primary domain’s URL was "www.altn.com" and WebConfig was listening on port 8083, then you could reach WebConfig by pointing you browser to "http://www.altn.com:8083". The WebConfig server can also be enabled or disabled from the Message Router.

MDConfig Security Issues (these do not apply to WebConfig)

Administrator

MDConfig must send this login and its accompanying password in order to gain administrator access to the remote configuration process. This level of access permits changes to every configuration aspect of MDaemon.

Password

This password must be provided along with the Administrator login in order to gain administrator access to remote configuration.

Supervisor

When this login with its accompanying password is sent by MDConfig, supervisor access to remote configuration will be granted. This level of access permits changes to accounts and account related functions within MDaemon such as auto-responders, account aliases, and account settings.

Password

This password must accompany the Supervisor Name in order for the client to gain supervisor level access to remote configuration.

Only allow connections from these IP’s

The IP addresses listed here are the only ones from which MDaemon will accept a remote configuration connection. Wildcards are permitted.

New IP address

To add an IP address from which you wish to allow Remote Configuration, enter the IP address here and then click the Add button.

Add

Click this button to add an IP Address that you have entered into the New IP Address text box.

Remove

Click this button to remove a selected IP address from the display window.

MDConfig backup directory

If specified, MDaemon will backup original copies of updated configuration files to this directory.


MDConfig - Remote Configuration Client

Introduction

The capability to remotely control MDaemon’s configuration parameters is fully supported using the MDConfig Remote Configuration Client. Utilizing a POP3-like proprietary protocol, a method exists whereby a client package such as MDConfig can connect to a running instance of MDaemon Server and mimic its configuration and setup. This makes it possible for MDConfig to alter the setup parameters of the host MDaemon. Once the desired configuration changes have been made, MDConfig reestablishes contact with the remote MDaemon site and uploads all the new changes, which will take effect immediately.

The steps involved are straightforward. A connection is made to a remote site that is running MDaemon. MDConfig and MDaemon exchange handshaking information, which includes a username and password for security (see Remote Configuration). Once the handshaking session is complete, the host MDaemon sends all of its configuration information and files to the remote MDConfig client. At this point MDConfig mimics the host MDaemon’s settings using all the familiar dialog boxes, buttons, and controls that users have come to expect when configuring MDaemon. Finally, after making any desired changes to MDaemon’s settings, MDConfig uploads all of the changes to the remote MDaemon site where they will be implemented.

Only one site can be remotely configured at a time. Once configuration information is provided from a remote site to MDConfig, it is not possible to gather configuration information from another site until the existing configuration session has been reset (see Resetting MDConfig for a New Connection below). In addition, it is very important to realize that changes to a site’s configuration information do not take effect until the changes are uploaded to the remote site (see Updating The Remote MDaemon Site). Further, if changes are made to the remote site’s configuration using the primary MDaemon interface while an MDConfig session is underway, those changes will not be reflected in the configuration information gathered by MDConfig at the start of the session and are likely to be overwritten when MDConfig updates the remote site. For this reason you must avoid making changes to MDaemon locally while it is being configured using MDConfig.

See:

Connecting to a Remote MDaemon Site

Updating the Remote MDaemon Site

Clearing Alterations without Updating the Remote Site

Resetting MDConfig for a New Connection

Moving MDConfig to Another Computer


Connecting to a Remote MDaemon Site

File|Connect…

This menu selection, or toolbar button, opens the Connect to MDaemon dialog on which you will specify the connection and security information needed to connect to MDaemon.

For a remote configuration session to be established, the remote MDaemon site’s Remote Configuration settings must match those supplied on this dialog.

Server Information

Server name or IP address

Enter the domain name or IP address of the MDaemon site to which you wish to establish a remote configuration session.

Administrator name

The value entered here must match the Administrator or Supervisor Name setting found on MDaemon’s Remote Configuration dialog.

Administrator password

The value entered here must match the Password corresponding to the Administrator or Supervisor Name being used. This setting is also found on MDaemon’s Remote Configuration dialog.

Use this port

Enter the port on which you have configured MDaemon to listen for MDConfig connections.

See:

MDConfig Remote Configuration Client

Updating the Remote MDaemon Site

Clearing Alterations without Updating the Remote Site

Resetting MDConfig for a New Connection

Moving MDConfig to Another Computer


Updating the Remote MDaemon Site

File|Update

Once you have finished modifying any MDaemon configuration parameters, choose this menu selection, or its corresponding button on the toolbar, to upload your modifications to the remote site. Since only one host can be configured at a time, pressing this button updates the last host from which configuration information was gathered.


Clearing Alterations without Updating the Remote Site

File|Reset

This function clears the workspace and prepares MDConfig to connect to a new remote MDaemon site. Any MDaemon settings currently displayed in MDConfig’s interface will be erased. Therefore, take care to update any changes to the remote site before resetting unless you wish to abort your configuration changes. Downloading MDaemon’s configuration and then Resetting or closing MDConfig without uploading the changes will in no way affect MDaemon nor alter any MDaemon settings.


Resetting MDConfig for a New Connection

File|Reset

This function clears the workspace and prepares MDConfig to connect to a new remote MDaemon site. Any MDaemon settings currently displayed in MDConfig’s interface will be erased. Therefore, take care to update any changes to the remote site before resetting unless you wish to abort your configuration changes. Downloading MDaemon’s configuration and then Resetting or closing MDConfig without uploading the changes will in no way affect MDaemon nor alter any MDaemon settings.


Moving MDConfig to Another Computer

To move MDConfig to another computer, copy the MDCONFIG.EXE and MDUSER.DLL files into their own directory on the other computer. Further, MDConfig uses CTL3D and Borland Custom Control DLL files. These files were installed along with MDConfig on the original computer. The files you need are CTL3D*.DLL, and BWCC*.DLL from the original computers Windows System directory. They need to be placed into the new computer’s Windows System directory, not in the same directory as MDCONFIG.EXE and MDUSER.DLL.  For Windows 95 systems, the directory is \windows\system. For NT4 machines it is \windows\system32.

Alternatively, you can use MDaemon’s executable installation file to install only MDConfig on the remote machine. Simply proceed through the normal MDaemon installation process but enable only the MDConfig installation option when asked which items to install.


WebConfig Remote Configuration Server

The WebConfig Remote Configuration Server makes it possible for administrators to edit all of MDaemon’s files and settings by using a web-browser. You can also assign limited WebConfig access to you users, enabling them to edit whichever of their individual account settings that you desire.

See:

Starting WebConfig

Logging on to WebConfig

Editing Personal Account Settings

Administrative Access

See Also:

Remote Configuration

Web Access Defaults

Account Editor|Web


Starting WebConfig

There are three ways to start/stop the WebConfig server:

1.	In the Statistics and Shortcuts frame on the right side of the Message Router, right-click on the WebConfig entry and choose the Toggle Active/Inactive selection on the shortcut menu.

2.	Click File | Enable WebConfig server.

3.	Click Setup | Remote Configuration… and then enable the control marked Enable WebConfig Remote...


Logging on to WebConfig

1.	Point your web-browser to http://primarydomain.com:WebconfigPort (designated on Ports).

2.	Type your MDaemon account’s logon and password.

3.	Click Logon.


Editing Personal Account Settings

This applies to accounts that do not have administrative access:

1.	Logon to WebConfig

2.	Edit whatever account settings to which you have access.

3.	Click the Save Changes button.

4.	Close your browser.


Administrative Access

	When a user who has been given administrative access logs on to WebConfig, they will see a navigation bar containing a number of options from which to choose. • Edit Config - Files that may be viewed and edited with WebConfig. • WC Status - Displays a list of server statistics and current status. • Account List - Displayed by default, this is a list containing information about each MDaemon account and buttons for editing or deleting them. • Add Account - This link takes you to a page used for adding an MDaemon user account. • Logout - Click this button when you are finished using WebConfig.


Account List

This page will be displayed by default when a user who has been given administrative access logs on to WebConfig.  It contains an entry for every MDaemon account.  Each entry contains the Email Address, the user’s Real Name, the number of Messages in the user’s mailbox, the Disk Space used, and the time and date of the Last POP Access from the account.  Each entry also contains an Edit and Delete button for editing or deleting the user’s account.


Editing/Deleting a User's Account

1.	Logon to WebConfig.

2.	Click the Edit or Delete button beside the Account List entry that you wish to edit/delete.

3.	If editing the account, make whatever changes you desire.

4.	Click the Save Changes button.

5.	Edit any other files or account settings as needed.

6.	Click Logoff when you are finished.


Adding a User Account

1.	Logon to WebConfig.

2.	Click Add Account on the navigation bar in the left frame.

3.	Enter the account information into the form that will be displayed.

4.	Click the Save Changes button.

5.	Click Logoff when you are finished.


Viewing MDaemon's Status

Click WC Status to display a table of WorldClient and MDaemon status and statistics.


Edit Config

This page displays a list and description of all files that can be edited using the WebConfig server. The list is built from a file called "Filelist.dat ", which is stored in the \mdaemon\WebConfig\ directory, and contains links to each of the files listed.


Filelist.dat

This comma-delimited file is used to build the list that is displayed when a user clicks Edit Config on the WebConfig servers navigation bar.  You can include in this list any filename that you choose, and use WebConfig to remotely access it.  Please provide complete paths to the files that you want to be able to access.

After each file path you can place an optional short description of the file, separated from it by a comma.  This description will be displayed on the Edit Config page just to the right of the filename to which it refers.  If you would like to make a listed file "View Only" then place a "Y" after the comment section (also separated by a comma).  Files with this character placed after the comments section will not be editable from the WebConfig server.

Each list of files is preceded by a header line, which gives some information about the upcoming group of files. For example,

Program=MDaemon, C:\MDaemon\App, MDaemon Configuration Files

This line contains three items. The ‘Program=NAME’ construct allows you to create a heading for groups of file names when they are displayed for configuration. Next comes a path value. This value is stored in a macro called $DIR$, which you can use to save some keystrokes when specifying individual files. The final section is a secondary header that will be displayed for reference.

Example:

Program=MDaemon, C:\MDaemon\App, MDaemon Configuration Files

$DIR$\app\MDaemon.ini, This is MDaemon’s ini file
$DIR$\app\CFilter.ini, This is MDaemon’s Content Filter ini file

Program=RelayFax, C:\RelayFax\App, RelayFax Configuration Files

$DIR$\RelayFax.log, These are read only notes, Y
$DIR$\accounts\customs.txt, This is a list customers, Y

Note the RelayFax section contains file entries that end with a Y character.  These items are read only—they can’t be edited.


Editing Files

Each entry’s file name is a link that will cause the file to be displayed in a text box for editing.  After you have made any desired changes to a file, click the Save Changes button.

Editing *.ini Files

INI files are treated differently on the Edit Config page. They are not simply opened in a text box for editing, but are instead opened in an editable form format.  When you include an INI file in your list then you can optionally create an additional file of the same name with the file extension "*.DSC".  This file is used for displaying a definition of each INI key, and controls several important factors that determine how some of the keys themselves will be displayed.

DSC (description) files contain the same entries as the INI files that they are describing.  But the value of each key should be a description or definition of the key instead of its corresponding INI value.

Example:

MDaemon.ini

[Domain]
DNSServer=127.0.0.1

MDaemon.dsc

[Domain]
DNSServer=This is the primary DNS server.

There are several other controls that can, and in some cases must, be included in DSC files:

•	[Heading]:Desc=[HeadingDescrition] - Use this format to cause a section heading to be displayed in bold with its description following.

•	[Key]=_DONOTSHOW_ - This will prevent the INI key from being displayed on the Edit Config page.

•	[Key]=[Description]_ENCRYPTED_ - This will cause the value of the INI key to be unencrypted/encrypted when it is displayed or saved.  For example: if your UserName is being encrypted by MDaemon then this would cause it to be unencrypted before it is displayed.  Without this control it would remain encrypted and you wouldn’t be able to tell what the actual UserName was.

•	[PasswordKey]=[Description]_ENCRYPTED_ _PASSWORD_ - This is the same as above except that it will also cause the displayed text to appear as "****".  This is usually used for passwords so that if someone were to look at your screen while you were typing it they wouldn’t be able to tell what your password actually was.

•	[Key]=[Description]_DISPLAYONLY_ - This will cause the value of the INI key to be "display only".  You will not be able to edit the key from the Edit Config page.

•	[SectionHeading]:NewKeys=_NONEWKEYS_- By default each section provides a text box for adding new INI keys to the file.  Use this control if you do not want anyone to be able to add a new INI key to a given section of the file.


Logout

Always click this button when you are finished using WebConfig.


WorldClient Standard

Included in MDaemon v3 is WorldClient Standard. WorldClient is a web-based email solution designed to offer users email client functionality using their favorite web browser. All of their email folders reside on the server so that they have access to everything as if they were at the office. WorldClient can easily hold its own against traditional mail clients while providing the added bonus of its ability to enable users to access their email from anywhere at anytime.

A few Application ideas:

•	Companies with mobile staff can keep them in touch with their email. Remember, WorldClient is not workstation dependent so "mobile" can also mean traveling across the building.

•	For the ISP that wants to offer web-based email services to their customer base. (Pro version recommended)

•	For the web-based email providers that will make their living from advertising banners. (Pro version recommended)

A few Administrator benefits:

•	Now you don’t have to configure and maintain each individual mail client.

•	Customize the graphical images used in WorldClient’s webpages to your corporate needs or the needs of your customer (for full customization at the HTML level, WorldClient Pro is required).

•	Gives your users the ability to maintain their own account settings thus saving you time. You can give as much or as little control to your users as you want.

A few User benefits:

•	Extensive email functionality wherever you can find a browser.

•	Client-side interface available in 12 languages. (Pro version only)

•	Personal and global address books, folders, send/receive file attachments, and much more.


Starting WorldClient

There are three ways to start/stop the WorldClient server:

1.	In the Statistics and Shortcuts frame on the right side of the Message Router, right-click on the WorldClient entry and choose the Toggle Active/Inactive selection on the shortcut menu.

2.	Click File | Enable WorldClient server on the Message Router.

3.	Click Setup | WorldClient Server… on the Message Router.


Logging in to WorldClient Standard

1.	Point your web-browser to http://primarydomain.com:WorldClientPort. This port is designated on the WorldClient Server Properties dialog.

2.	Type your MDaemon account’s logon and password.

3.	Click Logon.


Changing WorldClient Standard's Port Setting

1.	Click Setup | WorldClient Server… on the Message Router.

2.	Type the desired port in the control labeled Run WorldClient Server using this TCP Port.

3.	Click OK.


\MDaemon\WCStandard\

WorldClient.ini - All non user-specific settings for WorldClient are stored in the WorldClient.ini file. This file also contains the default settings for new WorldClient users. User specific settings are found in the User.ini located in the user’s subdirectory.

AddrBook.txt - This is the file used for building WorldClient’s Global Address Book. Personal Address Book entries are built from the AddrBook.txt file that is located in each user’s personal subdirectory.

Note
Address book files are Tab delimited. To add an Address Book entry, type: Full Name[Tab]email address[Tab][Return]. The entry will not be recognized unless there are tabs before and after the email address.


\MDaemon\WCStandard\HTML\

This subdirectory contains all of the GIF files used by WorldClient Standard, and a subfolder containing WorldClient Standard’s client-side help system. You may substitute the GIF files contained in this directory if you prefer a different "look", want to display your company logo, and so on. In order for your new graphics to be incorporated into the WorldClient Standard site, their filenames must be the same as the GIF files that they are replacing.

Note
Template customization with WorldClient Standard is not possible. To realize fully programmable, customizable templates, an upgrade to WorldClient Pro is required.

WCWatchInstaller.exe – This subdirectory also contains the WCWatch installer. WCWatch is a tray applet that can be downloaded by your users directly from within WorldClient. It runs in the background and checks for new mail by querying the WorldClient server directly, which eliminates the need to keep a browser open. It will check for new mail and inform you of unread messages in your mail folders, and it will launch your browser and automatically log you into WorldClient when you are ready to read your mail. WCWatch will configure itself when the user downloads it. Thus, there are no complicated instructions for your users to follow when they install it. See the WCWatch page under Options in WorldClient. For instructions on how to use WCWatch, see it’s online help system.


Client-side Help

WorldClient Standard is equipped with extensive client-side help for your users. See the online help system within WorldClient for information on the client features and functions.


WorldClient Server Properties

Use the Setup|WorldClient server… menu selection to enable your WorldClient server and to configure its settings. If you are using WorldClient Pro, the WorldClient Server Properties dialog also contains controls that govern the extent to which it and MDaemon will be synchronized.

WorldClient Standard/Pro Server Properties

Enable WorldClient server

Click this checkbox to enable the WorldClient server. You may also enable/disable WorldClient from the File menu or Statistics and Shortcuts frame of the Message Router.

Note
If you are using WorldClient Standard but have WorldClient Pro installed on the same machine, MDaemon will ask you if you want the controls on this dialog to apply to WorldClient Pro instead.

Run WorldClient server using this TCP port

This is the port on which WorldClient will listen for connections from your users’ web browsers.

Sessions not composing a message expire after xx inactive minutes

When a user is logged in to WorldClient but is not composing a message, this is the amount of time that their session may remain inactive before WorldClient will close it.

Sessions composing a message expire after xx inactive minutes

This timer governs how long a user’s session will be kept open while they are composing a message and the session remains inactive. It is a good idea to set this timer higher than the Sessions Not Composing a Message… timer since inactivity time is typically greater while a user is composing a message. This is because composing a message requires no communication with the server until the message is sent. Therefore, larger messages result in longer times of inactivity.

WorldClient Pro Only Options

The controls in this section apply exclusively to WorldClient Pro. If you do not have WorldClient Pro, this section can be disregarded. Visit www.WorldClient.com for more information about WorldClient Pro.

Use WorldClient Pro if it is installed on this Computer

Click this option if you have WorldClient Pro installed on the same machine as MDaemon and you would want this dialog’s controls to apply to it instead.

Stop & start WorldClient Pro when MDaemon stops & starts

Click this checkbox if you want MDaemon and WorldClient to always run at the same time. Stopping or starting MDaemon will automatically do the same to WorldClient.

Automatically synchronize accounts between MDaemon and WC Pro

Enable this control if you want MDaemon and WorldClient accounts to be automatically synchronized. Whenever an account is created or edited in MDaemon, the same account will be created or edited in WorldClient Pro. The reverse is true as well.

See:

MDaemon/WorldClient Pro Integration


RelayFax Integration

Alt-N Technologies’ RelayFax Server is an email to fax and fax to email gateway that can be seamlessly integrated with WorldClient Standard in order to provide its services to your users. When this functionality is enabled, WorldClient Standard users will be given access to various features that will enable them to compose and send faxes via the WorldClient Standard client pages. For more information visit the RelayFax web site at www.relayfax.com.

RelayFax Integration Options

Allow WorldClient user to send faxes through RelayFax

Enable this control in order to integrate RelayFax with WorldClient. When active it will cause a "Compose Fax" control and other fax related features to appear on the WorldClient pages.

Use SMTP to deliver faxes to RelayFax

RelayFax monitors a specific mailbox for incoming messages that are to be faxed. Click this option and MDaemon will use the normal SMTP email delivery process to send these messages to that mailbox’s address. This option is useful when RelayFax is monitoring a mailbox located somewhere other than your LAN. If RelayFax resides on your LAN you may choose to have MDaemon deliver the messages directly to RelayFax’s message queue and thus bypass the SMTP delivery process altogether. For more information on this method, see Directly deliver faxes into RelayFax’s incoming queue below.

RelayFax server’s email address

Specify the email address to which you want messages intended for faxing to be delivered. This value must match the address that you have configured RelayFax to monitor for these messages.

Directly deliver faxes into RelayFax’s incoming queue

If RelayFax resides on your LAN you may choose this method rather than SMTP for distributing messages to it for faxing. When MDaemon receives a messages intended for RelayFax it will place it directly into RelayFax’s incoming queue rather than deliver it using SMTP. If RelayFax resides on the same machine on which MDaemon is running you may leave the file path field blank. Otherwise, you must specify the network path to RelayFax’s \app\ directory.


MDaemon/WorldClient Pro Integration

WorldClient Pro has been specially designed so that it can be seamlessly integrated with Alt-N Technologies' MDaemon Server for Windows v3.1 Both WorldClient Pro v2.1.2 and MDaemon Version 3.1 use MDUSER.DLL to access MDaemon’s user management system. This functionality makes it possible to synchronize MDaemon and WorldClient accounts so that adding, editing, or deleting an account in WorldClient Pro will cause the same action to be performed in MDaemon. The reverse is true as well; account related actions performed in MDaemon will be mirrored in WorldClient Pro. This synchronization will also apply when changes are made using MDConfig or WebConfig.

By using this feature, you will no longer need to import/export accounts to or from MDaemon, nor will you need to duplicate account management actions when performed in one product or the other. When account synchronization is enabled in MDaemon, the first time that an existing MDaemon user logs in to WorldClient, a WorldClient account will be automatically created for them. This method is preferable since it slowly builds user accounts as needed rather than importing your entire user list, which may contain accounts that would otherwise never need to be imported.

In order to synchronize WorldClient Pro with MDaemon:

1.	Install both WorldClient Pro v2.1.2 or later and MDaemon v3.1 or later on the same machine. Synchronization requires both products to be installed on the same machine. Mapping another machine’s hard drive in not sufficient.

2.	In MDaemon, click the Setup menu and then WorldClient Server.

3.	Enable/check the checkboxes labeled Enable WorldClient Server, Use WorldClient Pro if it is Installed on this Computer, and Automatically Synchronize Accounts between MDaemon and WC Pro. You should also enable Stop & Start WorldClient Pro when MDaemon Stops & Starts if you would like to make sure that both programs are always running at the same time.

In the [Directories] section of the WorldClient.ini file, make sure that the MDaemonAppDir key exists and specifies the location of the MDaemon\app\ directory (e.g. MDaemonAppDir=C:\MDaemon\APP). This is the path to MDUSER.DLL. The key should be automatically created when synchronization is turned on in MDaemon.


MDaemon's Security and Screening Features

MDaemon is equipped with an extensive suite of security features and controls. Click the Setup|Security Settings menu to reach the following security features:

•	Address Suppression —Lists addresses that are not allowed to send mail traffic through your server.

•	AUTH/POP before SMTP —Many ISPs have begun to require their customers to perform a POP check or otherwise authenticate themselves before allowing them to send or receive mail through the ISP’s mail server. This feature makes it possible to do so.

•	IP Screening —Used to designate IP addresses from which you will allow or refuse connections to your server.

•	IP Shielding —If a domain name included in this list attempts to connect to your server, their IP address must match the one that you have specified.

•	Spam Blocker —Allows you to specify several ORBS/RBL type hosts that will be checked each time someone tries to send a message to your server. If the connecting IP has been blacklisted by any one of these hosts, the message(s) will be refused.

•	Relay Control —Used to control what MDaemon will do when a message arrives at your mail server that is neither from nor to a local address.


 Address Suppression

Use Setup|Security Settings|Address Suppression… to edit the addresses on the suppression list. This list contains addresses that are not allowed to send mail traffic through your server. If a message arrives from an address on this list, the message will be immediately deleted. This is useful for controlling problem users. Addresses may be suppressed on a per domain basis or globally (applied to all MDaemon domains).

Currently Suppressed Addresses

This window displays all currently suppressed addresses listed by the domain that is suppressing them.

New Suppression Entry

Domain name

Choose the domain to which this suppressed address will apply. In other words, what domain do you want to prevent from receiving mail from the suppressed address? Choose "All Domains" from this list to suppress the address globally.

Email address

Enter the address that you wish to suppress. Wildcards are accepted, therefore "*@badmail.com" will suppress any message from any user at "badmail.com" and "frank@*" will suppress any message from anyone named "frank", regardless of the domain the message is from.

Remove

Click this button to remove an entry that you have selected in the Currently Suppressed Addresses display.

Add

Click this button to add the designated user to the suppression list.

Options

Refuse to accept mail during SMTP session

If selected, mail to the selected domain from a suppressed address will be refused during the SMTP transaction stage. When this condition is set for a particular domain, no mail to that domain from a suppressed address will ever be stored on your server, even in temporary work files. This feature is set on a per domain basis.

Inform sender when their mail is rejected

If selected, a polite message will be routed back to the suppressed sender telling him or her that their message was deleted. This feature is set on a per domain basis.

Note
In order for this function to work, a copy of the message must be downloaded during the SMTP session so that it can be parsed. Consequently, this option is incompatible with the "Refuse To Accept Mail During SMTP Session" switch.


IP Screening

Use the Setup|Security Settings|IP Screening… menu selection to configure IP Screening. The IP Screen is a list of IP addresses that you have designated as either acceptable or non-acceptable. How the server treats attempted connections from the IP addresses listed on the IP Screen depends on the security setting selected in the Screen editor. You may specify a list of IP addresses and then configure the server to only allow connections from those on the list, or you can configure it to abort any connection attempt from an IP address on the list. Wildcards are acceptable in any of the four IP address positions:

*.*.*.*	Matches to any IP address

206.*.*.* 	Matches to any IP that begins with 206

206.97.*.239	Matches to IP addresses from 206.97.0.239 to 206.97.255.239

Current IP Screen Settings

This window displays all IP addresses that are being screened by MDaemon. They are listed either globally or according to the Local IP Address to which they apply.

New IP Screen Entry

Local IP

Choose from the drop-down list either "All IP’s" or the local IP to which you wish to apply the screen.

Remote IP

Enter an IP address that you wish to add to the screened list.  You must enter this address in dotted decimal form. The IP Screen works with IP addresses only. Click the Add button to add the specified IP address to the address listing.

This remote IP can connect

Selecting this option will allow only those IP addresses specified under the given domain to connect and deliver messages. Attempts to connect via IP addresses not specified in the listing will be refused and immediately aborted. This option is useful for setting up private mail network systems.

This remote IP can not connect

Selecting this option will allow all IP addresses other than those specified in the address listing to connect and deliver messages.  Attempts to connect from IP addresses specified in the address listing will be refused and immediately aborted.  This option is useful for excluding IP’s that cause problems for your mail transport system.

Add

Click this button to add the address specified in the IP Address control to the Current IP Screen Settings window.

Remove

Click this button to remove a selected entry from the listing.

Default for Undefined IP’s

Undefined IP’s can connect to this local IP

When this option is chosen, all IP addresses not listed in the IP Screen will be allowed to connect.

Undefined IP’s can not connect to this local IP

When this option is chosen, only those IP addresses specifically granted permission in the IP Screen will be allowed to connect.


 IP Shielding

Use the Setup|Security Settings|IP Shielding… menu selection to configure IP Shielding. The IP Shield is a list of domain names and matching IP addresses that will be checked during the SMTP MAIL FROM: command. An SMTP session claiming to be from someone at one of the listed domains will be honored only if it is coming from a machine with one of the associated IP addresses. For example, suppose your domain name is mdaemon.com and your local LAN computers use IP addresses in the range from 192.168.0.0 to 192.168.0.255. With this information you can setup the IP Shield to associate the domain name mdaemon.com with the IP address range 192.168.0.* (wildcards are allowed). Thus anytime a computer connects to your SMTP server and states, "MAIL FROM <someone@mdaemon.com>", the SMTP session will continue only if the connecting computer has an IP address within the required range from 192.168.0.0 to 192.168.0.255.

SMTP Message Sender Verification

Ensure sender’s address is valid if it claims to be from one of our domains

If the person sending a message claims to be from one of MDaemon’s domains, the account used will be verified against the account database. The local account must exist or MDaemon will refuse to accept the message for delivery.

POP Before SMTP

Local sender must have checked pop mailbox within last [xx] minutes

With this feature enabled, whenever someone claims to be a local user they must have logged in and checked their local mailbox within the specified number of minutes before they will be allowed to send mail.

Messages collected via ATRN are exempt from this requirement

Click this control if you want messages collected via ATRN to be exempt from the POP Before SMTP requirement.

ESMTP AUTH Command

Authenticated sender are valid regardless of the IP they are using

When this control is active, currently shielded IP addresses will not apply to users that have been authenticated. Mail will be accepted from them regardless of the IP address from which they are connecting.

Authenticated users are exempt from the POP before SMTP requirement

If you are utilizing the POP before SMTP security feature above, you may click this control to make authenticated users exempt from this restriction. An authenticated user will not need to perform a POP check before sending mail.

Global AUTH password

If the Authenticated senders are valid regardless of the IP they are using control is enabled, MDaemon accounts configured for dynamic NT authentication must use this global AUTH password for authentication instead of their normal NT password.

Currently Defined Domain/IP Pairs

This is the list of domain names and their corresponding IP addresses that will be compared when someone attempts to connect to MDaemon claiming to be from one of them.

Messages to valid local users are exempt from domain/IP matching

Click this option if you want only those messages that are destined for a non-local user or invalid local user to be checked for a domain/IP match. This will prevent others from posing as one of your local users in order to relay their mail through your server but save resources by not checking those sending messages to users on your server.

Domain name

Enter the domain name that you wish to associate with a specific IP address range.

IP address

Enter the IP address that you wish to associate with a domain name.  You must enter this address in dotted decimal form.

Add

Click the Add button to add the domain and IP address range to the listing.

Remove

Click this button to remove the selected entries from the listing.


ISP AUTH

As a security measure, many ISPs have begun to require their customers to perform a POP check or some other form of authentication before allowing them to send mail through the ISP’s mail server or dequeue the customer’s mail. The AUTH/POP Before SMTP feature makes it possible to fulfill this ISP requirement.

ISP Authentication

Use ESMTP AUTH when sending mail to ISP gateway

As an added security measure, some ISPs require their customers to log in using the ESMTP AUTH command before they are allowed to send mail through the ISPs servers. If your ISP requires you to do this then you can use the controls under this section to configure MDaemon to do so.

AUTH logon

Enter you AUTH logon here.

AUTH shared secret

This is the password used in the ESMTP AUTH command’s shared secret.


Dequeue AUTH

As a security measure, many ISPs have begun to require their customers to perform a POP check or some other form of authentication before allowing them to send mail through the ISP’s mail server or dequeue the customer’s mail. The AUTH/POP Before SMTP feature makes it possible to fulfill this ISP requirement.

Dequeue Authentication

Use ESMTP AUTH when sending dequeue signal to host

Besides requiring their customers to authenticate themselves before sending mail, some ISPs require their customers to authenticate themselves before sending the signal to dequeue any incoming mail that is being held for them.

AUTH logon

If authentication is required before sending the signal to dequeue your mail, this field is where you will place the required AUTH logon parameter.

AUTH shared secret

Enter the password used in the AUTH shared secret required by you ISP.


POP Before SMTP

As a security measure, many ISPs have begun to require their customers to perform a POP check or some other form of authentication before allowing them to send mail through the ISP’s mail server or dequeue the customer’s mail. The AUTH/POP Before SMTP feature makes it possible to fulfill this ISP requirement.

POP Before SMTP

Perform a POP check before sending waiting mail

Click this checkbox if you are required to perform a POP check before sending waiting mail.

Host name or IP address

Enter the host or IP address to which you wish to connect.

POP logon

This is the POP account’s logon or account name.

POP password

This is the account’s POP password.


Spam Blocker

Spam Blocker can be used to prevent most "spam" email from reaching your users. This new security feature allows you to specify several ORBS/RBL type hosts (which maintain lists of servers known to relay "spam") that will be checked each time someone tries to send a message to your server. If the connecting IP has been blacklisted by any one of these hosts, the message(s) will be refused or flagged.

Note
Use of this feature can prevent most spam from being sent to your users. However, some sites are blacklisted by mistake and therefore using this feature could cause some difficulties, but it is worthwhile if you are worried about controlling spam.

Spam Blocker lookups are performed using the DNS server specified in Setup|Primary Domain…|DNS. This feature was tested and performed well with no significant delay per mail session.

Spam Blocker includes an "exception" database for designating IP addresses that will not be subject to Spam Blocker lookups. Before activating this feature, you should add your local IP address range to the exception list to prevent lookups on it. 127.0.0.1 is exempt and therefore doesn’t need to be added to the exceptions.

For information on spam and how to control and eliminate it using ORBS and MAPS-RBL, visit:

http://www.orbs.org
http://www.mail-abuse.com/rbl/

ORBS and MAPS-RBL are trademarks of their respective organizations. Alt-N Technologies is proud to be associated with them and make use of their services on behalf of our customers.

Spam Blocker Engine

Enable spam blocker engine

Click this checkbox to turn on Spam Blocker.

Flag messages from blacklisted sites but go ahead and accept them

When this control is enabled, MDaemon will not refuse messages that receive a blacklisted result. However, those messages will have X-RBL-Warning: header inserted. You can then use the Content Filter feature to search for messages with this header and do with them as you please.

Check DomainPOP collected mail also

When this switch is enabled Spam Blocker will check the IP address stamped in the most recent "Received" header of downloaded messages.

Spam Blocker Hosts

MDaemon will query each of these hosts when performing a Spam Blocker lookup on an IP address. If a host replies to the query with a positive result, MDaemon will refuse to accept the message from that IP address, and will also send the short message associated with the host that blacklisted the address.

New host

If you wish to add a new host to be queried for blacklisted IP addresses, enter it here.

Message

This is the message that will be sent when an IP address has been blacklisted by the New Host.

Remove

Select an entry from the Spam Blocker Hosts list and click this button to remove it from the list.

Add

After entering a New Host and Message, click this button to add it to the Spam Blocker Hosts list.

Exceptions

Click this button to open the Spam Blocker Exceptions dialog on which you can designate IP addresses that will be exempt from Spam Blocker lookups. You should always include your local IP address range to prevent lookups on it. 127.0.0.1 is already exempt and therefore doesn’t need to be added to the list.

Caching

Click this button to open the Spam Blocker Caching dialog used for caching recent Spam Blocker results.


Spam Blocker Caching

Spam Blocker Caching Engine

Automatically cache spam blocker results

Enable this control if you want to cache those IP addresses that receive a positive (i.e. blacklisted) result from a Spam Blocker lookup.

• Warning!
Although caching addresses may conserve some resources—since Spam Blocker lookups will not need to be performed on those IP addresses which have already been cached—it is not recommended by the Spam Blocker Hosts. Since a blacklisted IP address could have its status corrected in a matter of minutes, caching entries could result in mail being refused unnecessarily. Therefore, caution should be used when caching entries. If you choose to use this feature then we recommend keeping the amount of time small that any given entry will be cached. For more information on the implications of caching Spam Blocker lookups, see: www.mail-abuse.org.

Enter New Cached Entry

IP address

Enter the IP address that you wish to manually add to the Spam Blocker cache.

Default time to live (in minutes)

This is the amount of time that the entry will remain in the Spam Blocker cache. Entering 9999 into this field will prevent the entry from expiring—however this is not recommended.

Maximum cached entries

This is the maximum number of entries that you want to allow to be cached.

Add

After entering the IP Address and Default Time To Live click this button to add the entry to the list of cached IP addresses.

Currently cached entries

This box lists the IP addresses that are currently cached. MDaemon will not perform a lookup on them. They will be treated as blacklisted addresses.

Remove

Select an entry and then click this button to remove it from the list of cached addresses.

Clear

Click this button the clear the list of all cached IP addresses.


Relay Control

Mail Relay Control

Use the Setup|Security Settings|Relay Control… menu selection to define how your server reacts to mail relaying.  When a message arrives at your mail server that is neither from nor to a local address, your server is being asked to relay (or deliver) the message on behalf of another user. If you do not want your server to relay mail for unknown users you can use the settings provided here.

This server does not relay mail for foreign domains

When this switch is selected, MDaemon will refuse to accept messages for delivery that are both FROM and TO a non-local user.

Refuse to accept mail for nonexistent local users

When this checkbox is enabled, MDaemon will refuse to accept mail that is for a local domain but addressed to a nonexistent user. "Local" includes both LAN and Gateway domains.

It’s OK to relay mail for aliases that include foreign domains

Click this control if you want MDaemon to relay mail for Address Aliases regardless of your Relay Control settings.

Domain and IP Permissions

Trusted domains

Domains that you list here are exceptions to the no-relay rule. These domains are "trusted" by your server and MDaemon will not refuse to relay mail for their users.

New trusted domain

Enter a new domain name to be added to the Trusted Domains list.

Add

Click this button to add the new domain to the Trusted Domains list.

Remove

Click this button to remove the selected entries from the Trusted Domains list.

Trusted IP addresses

IP addresses that you list here are exceptions to the no-relay rule.  These IP addresses are "trusted" by your server and MDaemon will not refuse to relay mail for their users.

New trusted IP address

Enter a new IP address to be added to the Trusted IP Addresses list.

Add

Click this button to add the new IP address to the Trusted IP Addresses list.

Remove

Click this button to remove the selected entries from the Trusted IP Addresses list.


Header Translation

Changing Header Text on the Fly

The "Outbound Domain Conversion" feature has been replaced with the "Header Translation" feature.  This new dialog can change any portion of text found within a header to a new value, whenever a message is detected which must leave your domain and travel across the Internet. Your old "Outbound Domain Conversion" settings will be migrated to this new "Header Translation" feature.  It works like this: You specify the text you want to search for and its corresponding replacement value.  MDaemon will then search through all the headers in the message and make the replacements. You may also specify headers that MDaemon should not modify (such as "Subject:" or "Received:" headers) by clicking the "Exceptions" button on this dialog.

This feature is necessary for some MDaemon configurations in which the local domain name is fictitious or different from the domain name that must appear on outbound mail. In such a situation, Header Translation could be used to change every occurrence of "@localdomain.com" to "@RemoteDomain.com".

This feature is much more powerful and versatile than the old "Outbound Domain Conversion" feature while retaining the same basic functionality.

Enter New Header Translation

Existing header text

Type the text that you want to be replaced when it is found within the headers of any outbound message.

New header text

This text will be substituted for that which you specified in the Existing Header Text field.

Add

Click this button to add the above text parameters to the Current Header Translations list.

Translate headers in forwarded messages

Click this checkbox to cause the header translations to apply also to messages automatically forwarded from a local domain to a non-local domain.

Currently Defined Header Translations

This list contains the portions of text that MDaemon will scan for in the outbound message headers, and the text that will be substituted when a match is found.

Remove

Select an entry in the Current Header Translations list and then click this button to remove it from the list.

Exceptions

Click this button to open the Header Translation Exceptions dialog. This dialog is used for specifying any Headers that you wish to be omitted from the Header Translation process.


Header Translation Exceptions

Do Not Translate Values in These Headers

Header value

Enter any header that you want to be omitted from the Header Translation process.

Add

Click this button to add a new header to the list.

Except These Headers

MDaemon will not scan these headers when it is substituting header text.

Remove

Select a header in the list and then click this button to remove it.


 IP Cache

In order to speed message delivery and shorten mail processing time MDaemon caches the IP addresses of all hosts with which it comes in contact. These IP’s are stored and the cache is checked each time MDaemon requires a DNS resolution on a domain name. If the domain name needing resolution is found in the IP cache then the DNS lookup is skipped, which can save a surprising amount of processing time. The settings in this window allow you to manipulate the parameters under which the cache will operate. You may also manually add and remove entries and set the maximum size of the cache. The IP Cache can be reached from the Setup|IP Cache… menu selection.

Create Cache Entry

Domain

Enter the domain name that you wish to add to the IP cache.

IP

Enter the IP address that you wish to add to the IP cache.

Add

Once you have manually entered a domain name and IP address, click this button to add them to the cache.

Caching Options

Clear cache at each processing interval

If selected, the entire contents of the cache will be flushed at the start of each mail session. This allows the cache to be refreshed at each processing interval.

Automatically cache uncached domains

This switch governs MDaemon’s internal auto-caching engine. If you want MDaemon to cache domains automatically then enable this option. If you want to build the IP Cache yourself, then clear this checkbox.

Default time to live

This is the default value in minutes that an entry in the IP Cache can survive. Once the entry has been in the IP Cache for this number of minutes, MDaemon will remove it.  If you want to set a permanent entry in the IP Cache then designate the Default Time To Live as 9999 in which case the entry will never expire.

Max cached entries

This value determines how large the cache may be. Once this setting has been reached, the next cache entry will bump the first one out of the cache.

Currently Cached IPs

Remove

Select an entry  in the Current Cached IP’s window and then click this button to remove it.

No cache

Click this button to bring up a list of domain names and/or IP addresses that you never want MDaemon to add to the IP Cache.

Clear

This button will flush the cache.


DNS Lookup

The DNS Lookup utility (Setup|Perform a DNS Lookup…) can be very useful when used in conjunction with the IP Cache. DNS Lookup makes it possible for you to quickly and easily perform a DNS lookup for any valid Internet domain name. A successfully resolved domain name lookup will display the domain’s A-Record and any MX-Records that might be listed. There is also a control that can be used to automatically add the results of a successful lookup to the IP Cache.

Host Information

Enter the domain name whose DNS information you wish to retrieve.

"A" Record Results

Add results to IP cache

Click this checkbox if you want the results of DNS lookups to be added to the IP Cache.

Domain name

This is the name of the resolved domain name.

Domain IP

This is the resolved domain’s IP address.

"MX" Record Results

This window will display any MX records listed for the resolved domain.

Lookup!

Click this button to perform a DNS lookup for the domain name that you have listed in the Host Information section.


 Send/Receive Scheduler

Click the Setup|Send/Receive Scheduler… menu selection to open MDaemon’s Send/Receive Scheduler. This dialog makes it possible for you to schedule MDaemon’s Local, Remote, RAW, and System mail processing events as extensively or as simply as you prefer. You can schedule exact times for mail delivery and collection and/or use a counter to process mail at regular intervals. You can also set conditions that will trigger mail processing at unscheduled times such as when a certain number of messages are waiting to be delivered, or when a message has been waiting a specified amount of time.

Local/RAW/System Mail Processing Interval

Slide this bar left or right to specify the time interval between mail processing sessions. It can be configured to count down from a range of 1 to 60 minutes, after which time MDaemon will Process Local, RAW, and System Mail before beginning the countdown again.  By default, this gauge only applies to Local, RAW, and System Mail. However, by checking the Deliver Remote Mail At This Inteval Also control it will apply to Remote Mail as well.  When this checkbox is cleared, Remote Mail processing intervals will be determined by the other scheduling controls on the Send/Receive Scheduler.

Deliver local mail immediately upon reception

When this option is selected, any Local, RAW, or System Mail will be processed and delivered each time an incoming SMTP session has completed.  This has the effect of instantaneous delivery of local messages.

Deliver remote mail at this interval also

If this checkbox is selected, the slide bar instead of the Scheduler will determine when Remote Mail is sent and/or collected. The rest of the controls in the Scheduler will be "dimmed" and will no longer apply to Remote Mail processing.

Simple Scheduling

There are numerous ways a remote mail session can be triggered in MDaemon. Several of them will be discussed here.  The Simple Scheduling feature is handy when you wish to setup a remote mail processing interval that should occur at a regular time interval after the last one regardless of the trigger that initiates the session. Unlike the rigidly fixed intervals used when setting up specific times or using the slide bar, this feature’s time interval will reset whenever mail is processed regardless of what caused the mail session to be initiated.

Note
In order for Simple Scheduling to take effect for a given day at least one timed entry must exist for that day in the Scheduled Times list. For example, suppose you wanted to schedule 45 minutes between dialup sessions but only on Monday through Friday. You would need to enable the Simple Scheduling option and enter 45 minutes into the control and then enter at least one scheduled time for each day (Monday, Tuesday, Wednesday, Thursday, and Friday). Since there would be no scheduled time for Saturday or Sunday, those days would be exempt and would not trigger a Remote Mail session. The hour and minute setting you designate when you setup your trigger days doesn’t matter; Simple Scheduling only checks whether there is an entry present for that day.

Scheduling Options

Always send mail if there’s xx or more messages waiting in the outbound queue

MDaemon will trigger a mail session whenever the number of messages waiting in the outbound queue meets or exceeds the number that you specify here. These sessions are in addition to any other normally scheduled sessions.

Always send mail if a waiting message is more than xx minutes old

When this control is enabled, MDaemon will trigger a mail session whenever a message has been waiting in the outbound queue for the number of minutes specified. These sessions are in addition to any other normally scheduled sessions.

Scheduled Remote Mail Processing Events

What day?

Select the days that you wish to schedule.

What hour?

Select the hour that you wish to schedule.

What minute?

Select the minute that you wish to schedule.

Add

Once you’ve selected the day, hour, and minute click this button to add this time to the list of scheduled events.

Remove

Clicking this button will remove an entry that you have selected from the schedule listing.

Clear all

This button removes all entries from the schedule listing.

RAS setup

This button is provided so that you can quickly review or edit your RAS settings.

TIP
The amount of time needed to load the Scheduler when MDaemon starts will vary.  The length of time this process will take is proportional to the number of event entries that have been created. Most configurations will do well to simply use the slide bar and Simple Scheduling to control mail processing intervals. For example, it is wasteful to schedule every minute of every day using the scheduler when you can simply set the slide bar to one minute intervals, place it in control, and accomplish the same thing. On the other hand, if you want the remote intervals to be further apart than the local intervals, but still frequent, then you could use Simple Scheduling for Remote and the slide bar for Local.

See:

RAS Dialup Settings


RAS Dialup Settings

Click the Setup|RAS Dialup/Dialdown… menu selection to configure your RAS Dialup Settings. This dialog will only be available if you have Remote Access Services installed on your system. It is used by MDaemon when you need to dial up your ISP just prior to a Remote Mail processing event.

The RAS Dialup Settings Dialog contains the following four tabs:

•	Dialup Settings

•	ISP Logon Settings

•	Post Connection

•	LAN Domains


Dialup Settings

Dialup Control

Enable RAS dialup/dialdown engine

Selecting this option will cause MDaemon to use the settings specified here to make a connection to a remote host before sending and/or receiving remote mail.

Dialup only if remote mail is waiting in outbound queue

When this switch is checked, MDaemon will not dial up the ISP unless there is remote mail waiting in the Remote queue. This may be beneficial in some circumstances but be aware that if MDaemon does not dial up then it cannot do any mail collecting either (unless it is delivered across the local LAN).

Notify [address] when dialup attempts fail

When selected, MDaemon will send a message to the specified address when a dialup event fails because of some error.

Dialup Attempts

Make this many attempts to establish a session

MDaemon will attempt to connect to the remote host this many times before giving up.

After dialing, wait this many seconds for a valid connection

This value determines how long MDaemon will wait for the remote computer to answer and complete the RAS connection.

Connection Persistence

Once established, MDaemon will not close the RAS session

By default, MDaemon will shut down a created connection immediately after all mail transactions have been completed, and the session is no longer in use. Selecting this option will cause the connection to remain open even after all transactions have been completed.

Note
MDaemon will never close a connection that it did not create.

Keep sessions alive for at least xx  minutes

If enabled, this option will cause an MDaemon created RAS session to remain open for at least the number of minutes specified or until all mail transactions have been completed, whichever is greater.


 ISP Logon Settings

Dialup Profile

Use any currently active dialup session

Click this checkbox if you want MDaemon to be able to utilize other connection profiles when it detects that one is active. Whenever it is time to dialup, MDaemon will first check to see if there is an active connection that it can use rather than dialing.

Logon name

The value specified here will be passed to the remote host during the authentication process.

Logon Password

The value specified here will be passed to the remote host during the authentication process.

Use this RAS dialup profile

This drop-down list box allows you to select a session profile that has been previously defined through windows Dialup Networking or Remote Access Services Setup.

New profile

Click this button to create a new Dialup Networking or Remote Access Services profile.

Edit profile

Click this button to edit the currently selected Dialup Networking or Remote Access Services profile.

Maximized Use

Maximize use of this connection profile

This switch causes MDaemon to monitor your connections so that if it detects that another program has established a connection it will process remote mail immediately regardless of scheduled times. If the connection remains open it will continue to process remote mail at regular time intervals based on the Use existing connection every XX minutes setting.

Hang-up now

This button will close the connection to the ISP. This button is active only if MDaemon has initiated the RAS session.


 Post Connection

Post Connection Process

Once connected, run this process

If a program is specified here, MDaemon will spawn a thread and execute the process. This is extremely useful for those who require Finger or some other program to unlock the ISP’s mailbox.

Pause server for xx seconds (-1 = infinite, 0=no waiting)

If the Once Connected, Run This Process control contains a valid entry then the server will pause its operations for the number of minutes specified here while it waits for the executing process to return. Entering "-1" will cause the server to wait indefinitely for the process to return.

Force process to shutdown after pause interval has elapsed

Sometimes the program you need to run may not exit once it has run its course; some programs require user intervention in order to close them down. This is not acceptable when the software must run unattended. If this switch is selected MDaemon will force the process thread to terminate once the number of seconds specified in Pause Server For XX Seconds has elapsed. This function does not work when the server is configured to wait indefinitely for the process to return.


 LAN Domains

These Domains Are On My Local LAN

The domains listed here are considered by MDaemon to be part of your local LAN. Therefore, no dialup is required in order to deliver a message to one of them.

New local LAN domain

Enter a domain name to add to the Local LAN list and click the Add button to add it.

Relay mail for these domains

If this switch is selected MDaemon will relay mail for these domains. This provides some measure of control over the traffic sent to and from these domains.

Add

Click this button to add an entry to the list of LAN domains.

Remove

Click this button to remove a selected entry from the list of LAN Domains.


LAN IPs

These IPs are on my local LAN

Like the LAN Domains tab, this tab is used to list IP addresses that reside on your LAN and thus do not require dialup in order to deliver messages to them. If a RAS session is in progress while messages are being delivered to these IP addresses and no non-local addresses remain, MDaemon will close the RAS session and continue to deliver the remaining Local IP messages.

Remove

Select an IP address from the list and then click this button to remove it. You may also double click an entry to remove it.

New local LAN IP

Enter an IP address to add to the local IP list and click Add. Wildcards like 127.0.*.* are permitted.

Add

After entering an IP Address into the New local LAN IP control, click this button to it to the list.


DomainPOP Mail Collection

Use DomainPOP Mail Collection (Setup|DomainPOP Mail Collection…) to configure MDaemon to download mail from a remote POP mailbox for redistribution to your users. This feature works by using the POP protocol to download all the mail found in the ISP’s POP mailbox associated with the specified logon. Once collected, the messages are parsed according to the settings provided on this dialog and then placed in user mailboxes or the remote mail queue for MDaemon to deliver, just as if the messages had arrived at the server using conventional SMTP transactions.

It is important to note that messages stored in POP mailboxes and retrieved using the POP protocol will be devoid of the important routing information (sometimes called the message’s "envelope") that would ordinarily be supplied had the messages been delivered using the more powerful SMTP protocol. Without this routing information, MDaemon is forced to "read" the message and examine the headers in an attempt to determine to whom the message was originally intended. This is not an exact science to say the least. Message headers are sometimes notorious for their lack of sufficient information that is needed to determine the intended recipient. This lack of what would seem to be a fundamental characteristic of an email message - the recipient - may seem surprising but one must keep in mind that the message was never intended to be delivered to its recipient using the POP protocol. With SMTP, the contents of the message are irrelevant since the protocol itself dictates specifically to the server, during the mail transaction, the intended recipient of the message.

In order to allow for POP retrieval and delivery of mail messages in a reliable and consistent way, MDaemon employs a powerful suite of header processing options. When MDaemon downloads a message from a remote POP source it immediately parses all the relevant headers within that message and builds a collection of potential recipients. Every email address found in the headers that MDaemon inspects is included in the collection.

Once this process is complete, MDaemon’s collection of recipients is divided into local and remote sets. Further, all addresses that are parsed and placed into the collection of potential recipients are processed through the Address Alias translator before being divided into local and remote sets. Every member of the local set (addresses with a domain that matches either MDaemon’s Primary domain or one of the Secondary domains) will receive a copy of the message. What happens to the remote set is governed by the settings in this dialog. You can elect to simply ignore these addresses, forward a summary listing of them to the postmaster, or honor them—in which case MDaemon will actually deliver a copy of the message to the remote recipient. Only under rare circumstances would the need to deliver these messages to remote recipients be warranted.

Care must be taken to prevent duplicate messages or endlessly looping mail delivery cycles. A common problem that results from the loss of the SMTP envelope manifests itself with mailing list mail. Typically, messages distributed by a mailing list do not contain within the message body any reference to the addresses of the recipients. Rather, the list engine simply inserts the name of the mailing list into the TO: field. This presents an immediate problem: if the TO: field contains the name of the mailing list then the potential exists for MDaemon to download this message, parse the TO: field (which will yield the name of the mailing list), and then dispatch the message right back to the same list. This would in turn deliver another copy of the same message back to the POP mailbox from which MDaemon downloaded the original message—thus starting the whole cycle over again. To cope with such problems mail administrators must take care to use the tools and settings that MDaemon provides to either delete mailing list mail or perhaps alias it in such a way that it will be delivered to the proper local recipient(s). You could also utilize the Routing Rules or Content Filters to deliver the message to the correct recipient(s).

Additional concerns when employing this sort of mail collection scheme revolve around the issue of unwanted message duplication.  It is very easy for mail that is delivered to the ISP’s POP mailbox using SMTP to generate unwanted duplicates, once it has been collected using DomainPOP. For example, suppose a message is sent to someone at your domain and a carbon copy is sent to another person at the same domain. In this situation, SMTP will deliver two copies of the same message to your ISP’s mailbox—one for each recipient. Each of the two message files will contain references to both recipients—one in the TO: field and the other in the CC: field. MDaemon will collect each of these two identical message files and parse both addresses from each of them. This would result in both recipients receiving one unwanted duplicate message. To guard against this sort of duplication MDaemon uses a control which allows you to specify a header that MDaemon will use to check for duplication. The Message-ID field is ideal for this. In the above example, both messages are identical and will therefore contain the same Message-ID field value. MDaemon can use this value to identify and remove the second message during the download stage before it can be parsed for address information.

As a final measure guarding against duplicate messages and endless looping delivery cycles, MDaemon employs a means for detecting how many trips or "hops" a message has made through the transport system. Each time an SMTP mail server processes a message it "stamps" the message with a "Received" header. MDaemon counts all such headers when it encounters a message for the first time. If the total number of mail servers exceeds a specified value, it is likely the message is caught in a delivery loop and should be taken out of the mailstream and moved to the bad message directory. This value can be configured through the Domain Configuration Editor.

See:

Primary Domain Configuration

Content Filters

Mailing Lists


 Account

DomainPOP Host Properties

Enable DomainPOP mail collection engine

If selected, MDaemon will use the setting provided on this screen to collect mail from a DomainPOP mail host for local redistribution.

Host name or IP

Enter your DomainPOP host’s domain name or IP address here.

Logon name

Enter your login of the POP account used by DomainPOP.

Password or APOP shared secret

Enter the POP account’s password or APOP shared secret here.

Use APOP

Click this box if you wish to use the APOP command and CRAM-MD5 authentication when retrieving your mail. This makes it possible to authenticate yourself without having to send clear text passwords.

Mail Download Control

Leave a copy of message on host server

If selected, MDaemon will not remove collected messages from your DomainPOP mail host.

Delete messages once [XX] or more have accumulated (0 = no limit)

If you are leaving messages on your ISP server then they will be deleted once this number is reached.  Enter "0" if you want messages to remain on the server regardless of the number.

Note
Some ISP’s may limit the amount that you are allowed to store in your mailbox.

Don’t download messages larger than [XX] KB (0 = no limit)

Messages greater than or equal to this size will not be downloaded from your DomainPOP mail host.  Enter "0" if you want MDaemon to download messages no matter the size.

Delete large messages from DomainPOP and MultiPOP hosts

Click this switch and MDaemon will delete messages that exceed your maximum set size.  The messages will simply be removed from the DomainPOP and MultiPOP mail hosts and will not be downloaded.

Warn postmaster about large DomainPOP messages

Click this switch and MDaemon will send a warning to the postmaster whenever a large message is discovered in the DomainPOP mailbox.

Download messages according to size (small messages first)

Enable this checkbox if you want the message downloading order to be based on size—beginning with the smallest and proceeding to the largest.

Note
This option retrieves smaller messages quicker but requires a larger amount of internal sorting and processing.

Over Quota Accounts

Warn account holder and delete over quota message

When this option is chosen and a message is collected for an account that is over its quota (designated on the Quotas tab of the account editor), MDaemon will delete the message and send a warning to the user letting them know that their account is over its limit.

Warn account holder and forward over quota message to Postmaster

When this option is chosen and a message is collected for an account that is over its quota (designated on the Quotas tab of the account editor), MDaemon will forward the message to the Postmaster and send a warning to the user letting them know that their account is over its limit.


 Parsing

Parsing Properties

Dedupe collected mail using the message-id field

If this option is selected MDaemon will remember the value of the specified header and will not process additional messages collected in the same processing cycle which contain an identical value. The Message-ID field is the natural header to use but the actual header can be anything you want.

Parse "Received" headers for email addresses

This switch makes use of a powerful yet seldom used optional RFC-822 regulation. It is possible to store the recipient information ordinarily found only within the message’s envelope in a message header so that parsers of the mail message will be able to glean the actual recipient address by merely inspecting the headers later. MDaemon will attempt to capitalize on this optional rule if you have this switch set by parsing ALL the "received" headers found within the mail message for valid addresses.

Skip over the first xx "received" headers

Sometimes it is useful to process Received headers but starting at the nth occurrence of them.  This setting allows you to enter the number of "Received" headers that MD will skip over before beginning its processing.

Stop parsing if "received" yields a valid local address

If while parsing a "received" header MDaemon detects a valid local address, this switch will cause all further parsing to stop and MDaemon will not search the message for more potential delivery addresses.

Parse "subject:" header for address inside "(" and ")" characters

When this is selected and MDaemon finds an address contained in "( )" in the "Subject:" header of a message, this address will be added to the message’s list of recipients along with any other parsed addresses.

Parse these headers for email addresses

This control lists the headers that MDaemon will parse in an attempt to extract addresses.  Every header listed here is checked for addresses.

Remove

This button will remove the selected entries from the header list.

Default

This button will clear the current contents of the header list and add MDaemon’s default list of headers. The default headers are typically sufficient to extract all addresses from the message.

New header

Enter the header you wish to add to the header list.

Add

Add the header listed in the New Header control to the list.


 Processing

Domain Name Replacement

Enable domain name replacement engine

This option is an attempt to cut down on the number of domain aliases your site will require.  When a message is downloaded *all* domain names in *all* addresses which are parsed from that message are instantly transformed into the one specified here.

Ignore unknown local addresses parsed from messages

As mentioned above, the Domain Name Replacement feature will alter the domain name in all email addresses parsed from the message, converting it into the one you specify on this screen.  This could create some addresses which do not have a corresponding mailbox account at your site.  Since the domain name will match your primary domain name, MDaemon will consider such addresses local but undefined.  Such mail typically generates a "No Such User" message directed at the postmaster.  This switch will prevent the Domain Name Replacement Engine from generating "No Such User" messages.

Address Filtering

Always strip the following text from all parsed addresses

Some ISP’s will stamp each message with a line that indicates who the recipient of the message should be along with a bit of routing information appended to the address on either the left or right hand side.  This stamp would be perfect to use for parsing the recipient address except that the additional routing information makes this impossible without a lot of account aliasing.  Rather than do all that you can simply specify the value of this appended text in the edit control associated with this feature and MDaemon will strip any occurrence of this text from all addresses that it parses.


 Routing Rules

Existing Rules

This list shows you the rules that you have created and will be applied to your messages.

Remove

Press this button and the selected rules in the Existing Rules list will be removed.

Default

Press this button to remove all existing rules and replace them with a predefined set of defaults.

Clear all

This button removes all existing rules.

New Rule

If the parsed address…

Is equal to, is not equal to, contains, does not contain

This is the type of comparison that will be made when an address is compared to this routing rule. MDaemon will search each address for the text contained in the "This text" field and then proceed based upon this control’s setting—does the address’s complete text match exactly, not match exactly, contain the text, or not contain it at all?

This text

Enter the text that you want MDaemon to search for when scanning the addresses.

Then do this with the message

This control lists the available actions that can be performed if the result of the rule is true.  Here is a list of actions and what they do:

Don’t deliver to this address - Selecting this rule will prevent the message from being delivered to the specified address.

Send to user or group of users - Selecting this action will bring up a dialog that will allow you to create a list of email addresses that should receive a copy of the message being processed.


 Foreign Mail

What to do with non-local mail

Forward summary of non-local addresses to postmaster

If this option is selected MDaemon will send a single copy of the message to the postmaster along with a summary of the non-local addresses that the parsing engine extracted using the current set of headers and parsing rules.

Deliver non-local mail to all remote recipients

If this option is selected MDaemon will deliver a copy of the message to any non-local recipient that it finds within the inspected headers.

Do not deliver mail addressed to non-local addresses

If this option is selected MDaemon will remove from the recipient list any address that is non-local. It will be as if MDaemon never parsed remote addresses from the original downloaded message.

Note
The various Unless.. buttons allow you to define addresses which are exceptions to the rules.


 Security

Safety Options

Place an extra copy of all downloaded mail into this directory

This is a safety feature to ensure that you don’t lose any mail due to unforeseen parsing or other errors that might occur when downloading mail in bulk quantities.


 Name Matching

Note
The Name Matching feature is only active in conjunction with the DomainPOP Mail Collection engine. If you wish to use this feature, you must make sure that you have DomainPOP enabled. DomainPOP can be reached from the Setup|DomainPOP Mail Collection menu selection.

Real Name Matching Engine

Activate real name matching engine

This feature allows MDaemon to determine who should receive a DomainPOP collected message based not upon what the email address is but upon what the text portion (typically a person’s real name) is.  For example, a message’s TO header might read:

TO: "Joe User" <common-mailbox@isp.com>

or

TO: Joe User <common-mailbox@isp.com>

Name Matching does not care about the "common-mailbox@isp.com" portion of the address.  It instead extracts the "Joe User" portion and attempts to lookup this name in the MDaemon user database.  If a match is found to an account’s real name field then that account’s local email address is used for delivery purposes.  If no match is made then MDaemon reverts to delivering the message to the email address parsed from the data (common-mailbox@isp.com in this example).

Note
The real name portion of the address should not contain a comma, semi-colon, or colon character so take care when you setup this information in your mail clients.

Only apply this feature if the address portion matches this value

This control allows you to specify an email address that must be present in the extracted data in order for the real name matching process to proceed.  This allows you a measure of control over when the Name Matching feature will be employed.  For example, you can specify an address such as "common-mailbox@isp.com" and then only addresses matching this value will be candidates for Name Matching.

Suppose you have "common-mailbox@isp.com" in this control.

This means that:

TO: "Joe User" <common-mailbox@isp.com> will be a candidate for Name Matching while TO: "Joe User" <Joe@mdaemon.com> will not.


Content Filter

The Content Filter dialog (Setup|Content Filter…) can be used for a large number of purposes such as: preventing spam email, catching viruses before they reach their final destination, copying certain emails to one or more additional users, appending a note or disclaimer to the bottom of messages, adding, modifying, or deleting headers, stripping email attachments, deleting certain messages, and more. Because individual Content Filter rules are created by the administrator, and because of their diversity, they can be used in many situations and are limited for the most part only be the creativity of the person creating them. With a little bit of thought and experimentation, this feature can be very useful.

All messages processed by MDaemon at some point arrive in one of the message queues.  When Content Filtering is enabled, before any message is allowed to leave the queue in which it is being held, it will first be processed through the Content Filter rules. The result of this procedure will determine what is done with the message.

Note
Messages that have a filename beginning with the letter "P" will be ignored by the content filtering process. Every other message will be processed through the content filter system. Once processed, MDaemon will change the first character of the filename to a "P". In this way a message will only be processed through the content filtering system once.

See:

Content Filter Editor

Creating a New Content Filter Rule

Modifying an Existing Content Filter Rule


Content Filter Editor

Content Filter Engine

Enable content filtering engine

Click this checkbox to enable content filtering. All messages processed by MDaemon will be filtered through the content filter rules before being delivered.

Scan no more than [xx] KB of the message

Enter the maximum number of Kilobytes that you want the content filtering system to scan in each message for comparing to the filter rules. Scanning will start at the top of the message and proceed until this amount is reached, then MDaemon will move to the next message. Setting this value to "0" will cause the entire message to be scanned regardless of the size.

Existing Content Filtering Rules

This box lists all rules in the order that they will be applied to a message. This makes it possible for you to arrange your rules to achieve a greater level of versatility.

For example: If you have a rule that deletes all messages containing the words, "This is Spam!" and a similar rule that sends those messages to the Postmaster, then putting them in the right order will enable both rules to be applied to the message. This assumes that there isn’t a "Stop Processing Rules" rule that applies to the message higher up in the list. If so, then you would use the Move Up/Move Down buttons to move the "Stop" rule below the other two. Now any message containing "This is Spam!" would be copied to the Postmaster and then deleted.

Note
New to MDaemon Version 3 is the capability to create rules that will perform multiple tasks and use and/or logic. Therefore, considering the example above, you can now create a single rule that will accomplish all of those tasks and more.

New rule

Click this button to create a new content filter rule. This will open the Setup New Rule dialog.

Edit rule

Click this button to open the selected rule in the Modify Rule editor.

Copy rule

Click this button to clone the selected content filter rule. An identical rule will be created and added to the list. The new rule will be given a default name called "Copy of [Original Rule Name]". This is useful if you wish to create multiple similar rules. You can create a single rule, clone it several times, and then modify the copies as needed.

Delete rule

Click this button to delete the selected content filter rule. You will be asked to confirm your decision to delete the Rule before MDaemon will do so.

Move up

Click this button to move the selected rule up.

Move down

Click this button to move the selected rule down.

Rule Description [Rule Name] (Enabled/Disabled)

This box displays the currently selected rule in its internal script format. Click any of the rule’s conditions (listed as a hyperlink) and the appropriate editor will be opened for changing that particular condition.

See:

Creating a New Content Filter Rule

Modifying an Existing Content Filter Rule


Creating a New Content Filter Rule

This dialog is used for creating Content Filter Rules. It is reached by clicking the New Rule button on the Content Filter dialog.

Give This Rule a Name

Type a descriptive name for your new rule here. By default it will be called "New Rule #n".

Define New Content Filter Rule

Select conditions for this rule

This box lists the conditions that may be applied to your new rule. Click the checkbox corresponding to any condition that you want to be applied to the new rule. Each enabled condition will appear in the Rule Description box below. Most Conditions will require additional information that you will specify by clicking on the Condition’s hyperlink in the Rule Description box.

If the [HEADER] contains—Click any of these options to base your rule on the content of those particular message headers. You must specify the text for which to scan.

If the user defined [# HEADER] contains—Click one or more of these options to base the rule on message headers that you will define. You must specify the new header, and the text for which to scan.

If the MESSAGE BODY contains—This option makes the contents of the message body one of the conditions. This condition requires you to specify a text string for which to search.

If the MESSAGE has Attachment(s)—When this option is selected, the rule will be contingent upon the presence of one or more message attachments. No additional information is required.

If the MESSAGE SIZE is greater than—Click this option if you want the rule to be based upon the size of the message. The size must be specified in KB. Default is 10KB.

If the MESSAGE HAS A FILE called—This option will scan for a file attachment with a particular name. The filename must be specified.

If the MESSAGE IS DIGITALLY SIGNED—The condition applies to messages that have been digitally signed. No further information is required by this condition.

If ALL MESSAGES—Click this option if you want the rule to be applied to all messages. No further information is required; this rule will affect every message except those to which a "Stop Processing Rules" or "Delete Message" action has been applied in a previous rule.

Select actions for this rule

MDaemon can perform these actions if a message matches the rule’s conditions. A few Actions will require additional information that you will specify by clicking on the Action’s hyperlink in the Rule Description box.

Delete Message—Selecting this action will cause the message to be deleted.

Strip All Attachments From Message—This action causes all attachments to be stripped from the message.

Move Message To Bad Message Directory—Click this action to cause a message to be moved to the bad message directory.

Skip n Rules—Selecting this action will cause a specified number of rules to be skipped. This is useful in situations where you may want a rule to be applied in certain circumstances but not in others.

For example: you may wish to delete messages that contain the word "Spam", but not those that contain "Good Spam". To accomplish this you could create a rule that deletes messages containing "Spam" and then place above it another rule that states "if the message contains "Good Spam" then Skip 1 Rule".

Stop Processing Rules—This action will skip all remaining rules.

Copy Message To Specified User(s)—Causes a copy of the message to be sent to one or more recipients. You must specify which recipients are to receive the message.

Append Standard Disclaimer—This action makes it possible for you to create a small amount of text that will be appended as a footer to the message. Alternatively, it can add the contents of a text file.

For example: you could use this rule to include a statement that says "This email originated from my company, please direct any complaints or questions to me@mycompany.com".

Add Extra Header Item To Message—This action will add an additional header to the message. You must specify the name of the new header and its value.

Delete A Header Item From Message—This action will remove a header from a message. You must specify the header that you wish to delete.

Send Note To... —This action will send an email to a particular address. You will be able to specify the recipient, sender, subject, and a small amount of text. You can also configure this action to attach the original message to the note.

For example: you might wish to create a rule that will move all messages containing "This is Spam!" to the bad message directory and create another rule that will send a note to someone letting them know that this has been done.

Remove Digital Signature—Click this action to cause a digital signature to be removed from the message.

Run Process…—This action can be used to run a particular program when a message meets the rule’s conditions. You must specify the path to the program that you wish to run. You can use the $MESSAGEFILENAME$ macro to pass the name of the message to the process, and you can specify whether or not MDaemon should suspend its operations temporarily or indefinitely while it waits for the process to terminate. Further, you can force the process to terminate and/or run it in a hidden window.

Send Message Through SMS Gateway Server…—Click this option to send the message through an SMS Gateway Server. You must supply the Host or IP Address and the SMS phone number.

Copy Message to Folder…—Use this option to place a copy of the message into a specific folder.

Rule description

This box displays the new rule’s internal script format. Click any of the rule’s conditions or actions (listed as hyperlinks) and the appropriate editor will be opened for specifying any needed information.

See:

Content Filter Editor

Modifying an Existing Content Filter Rule


Modifying an Existing Content Filter Rule

To modify an existing content filter rule, select the rule and then click the Edit Rule button on the Content Filter dialog. The rule will be opened for editing in the Modify Rule editor. The controls on this editor are identical to the Create Rule Dialog.

See:

Content Filter Editor

Creating a New Content Filter Rule


 Priority Mail

The Setup|Priority Mail… menu selection opens the Priority Mail dialog, which is used to define what constitutes Priority Mail on your system. Priority mail is delivered immediately by MDaemon regardless of scheduled mail processing intervals. When a new message arrives, MDaemon inspects its headers for a set of header/value combinations that you have specified on this dialog. If it finds them, it considers the message a high priority item and attempts to deliver it immediately.

Priority Mail Engine

Enable priority mail checking engine

Click this switch to enable the Priority Mail feature. MDaemon will inspect incoming messages for priority status.

Enter New Header/Value

Header

Enter the message header in this field. Do not include the ending colon character.

Value

Enter the value that must be found in the specified header in order for the message to be considered high priority.

Trigger even if value is a sub-string

When entering a new Priority Mail setting you may select this feature to enable priority matching of a portion (or sub-string) of a header value. For example, you could create a Priority Mail Setting for the "To" header with the value "Boss". Then, any email containing "Boss@anything" in that header would be considered Priority Mail. If an entry is created without this feature enabled then the value of the header must match the entry exactly; matching only a portion will not be sufficient.

Add

After entering the Header/Value information in the specified text boxes, and after specifying whether this entry will apply to sub-strings, click the Add button to create the new Priority Mail entry.

Current priority mail header/value pairs

This window lists all the currently defined priority mail header/value combinations.  Double click on an item in this list to remove it.

Remove

Click this button to remove a selected entry from the Current Priority Mail Settings window.

Exceptions

This allows you to define field/value combinations that will cause a message to be considered an exception to the priority mail settings. This gives you more flexible control over this feature.


 Log File

Click the Setup|Log File… menu selection to configure your Log File settings.  The log file is a useful tool for diagnosing problems and seeing what the server has been doing while unattended.

Logging Mode

Log each day in its own file

If this option is selected then a separate log will be generated each day.  The name of the file will be "MD[YYYYMMDD].LOG".

Log each day by day of week

If this option is selected, a separate log will be generated for each day of the week. The name of the log files will be DAYOFWEEK.LOG (e.g. Monday.log, Tuesday.log, and so on).

Log everything in one file

Enable this switch to log all entries in a single file.

File name

If you elect to use the Log Everything In One File option then specify the name of the log file here. The log file will be stored in the Logs directory.

Log File Size

Max log file size [xx] KB

This is the maximum size in kilobytes that a log file may reach. Once this size is reached, the log file is copied to LOGFILENAME.OLD and a new log is started.

Perform no more than one automatic backup per day

When limiting the log file size, click this checkbox if you want no more than one log file to be backed up per day. Each day, the first time that the maximum log file size if reached it will be renamed to "*.OLD" and saved normally. The subsequent log file will continue to grow regardless of the maximum size specified. It will not be rolled over until the next day—even if the maximum size setting is surpassed.

Logging Options

Log detailed mail sessions

A complete transcript of each mail transaction session will be copied to the log file when this option is active.

Log summarized mail sessions

The option causes a summarized transcript of each mail transaction session to be copied to the log file.

Track sessions in real time

Ordinarily, session information is logged after the session is completed in order to conserve resources. Click this option if you want session information to be logged as in occurs.

Include parsing activities

There is a lot of message file parsing that MDaemon must periodically perform. Enable this switch if you want this information to be included in the log file.

Include RAS transcripts

Select this switch if you want MDaemon to copy RAS dialup/dialdown activities into the log file. This information is useful for diagnosing dialup problems.

Include POP TOP processing

Select this switch if you want MDaemon to copy POP TOP information into the log file.


 System Service Settings

Use the Setup|System Service Settings…  menu selection to run MDaemon as a system service under Windows NT/2000 or Windows 95/98. MDaemon will detect if you are running Windows 95/98 and present a different Service Setup Dialog if you are. Although much less sophisticated than under NT/2000, services in Windows 95/98 will still allow you to operate the software without anyone being logged on.

Service Options

Run MDaemon as a Windows NT system service

Enables the MDaemon service feature.

Service name

This is the name that NT will use for the service.

Start service

This is the initial state of the service.

Dependencies

A list of Services that must be active before the MDaemon service should attempt to load.


Network Resource Access

When running MDaemon as an NT/2000 system service, by default it runs under the LocalSystem account. Because this account does not have access to network devices, MDaemon will not be able to access mail if you wish to store it on other computers across your LAN. That is, not unless you provide logon credentials for an account that can be used to provide the MDaemon service access to network shares. We recommend creating a user account specifically designed for running MDaemon with whatever restrictions that you desire, but which has access to those network shares that you want MDaemon to be able to use. That way you can access network shares with UNC notation or mapped drives when running MDaemon as a service. Further, all applications launched by MDaemon (e.g. MDStats and Pre-Processing utilities) will also use the security context of this same NT Account.

Logon name

This is the logon name of the NT Account under which the MDaemon service should run.

Password

This is the NT Account’s password.

Domain

This is the NT Domain on which the account resides. Leave this field blank to logon to the default domain.


GUI

GUI Properties

Use small display font on router & session windows

Enables the small display font on the Router and Session windows.

Clear message counts at startup

When this checkbox is enabled, the message statistics information displayed on the main router window will be reset whenever MDaemon is launched.

Minimize to task bar in addition to system tray

Clear this checkbox if you do not want MDaemon to appear on the Windows taskbar when the program is minimized; only the tray icon will be visible. When this control is enabled and MDaemon is minimized it will appear on both the taskbar and in the system tray.

Restrict MDStats GUI to a single instance only

Click this checkbox if you do not want more the one copy of MDaemon’s queue and statistics manager to be able to run at once. Attempting to launch MDStats when it is already running will simply cause the currently running instance to become the active window.

MDStats shows queue and mail directory subfolders

Click this checkbox if you want the queue statistics manager to display subfolders contained in the various queues and user mail directories.

Max number of accounts shown in GUI controls (0=show all)

This is the maximum number of accounts that will be shown in the drop-down list boxes on various dialogs. Further, when the value in this control is set to anything other than "0" (show all) the "Edit Account" and "Delete Account" options will no longer appear on the Accounts menu. Those functions will only be available from the Accounts Manager. You must restart MDaemon before any changes to this control will go into effect.

Max domains listed in tool window controls (0=show all)

This is the maximum number of secondary domains that will be listed under the "Servers" controls in the main display’s tool window. After changing this value, you must press F5 or restart MDaemon before the change will be visible in the tool window. This control cannot be set to anything less than 50.

Max number of log lines displayed before router window refresh

This is the maximum number of lines that will be displayed in the log window of the main display. When this number of lines is reached the window will be cleared. This has no affect on the log file. Only the display will be cleared.

Max number of log lines displayed before session windows refresh

This is the maximum number of lines that will appear in each session Connection window before it is cleared. This has no affect on the log file.

Start MDaemon…

In the system tray

Choose this option if you want MDaemon’s interface to be minimized at startup.

In a maximized window

Choose this option if you want MDaemon’s interface to be maximized at startup.

In a default window

Choose this option if you want MDaemon’s interface to appear in a default window at startup.

Create Session…

In a minimized window

If this option is selected MDaemon will create new mail session windows in a minimized state.

In a hidden window

If this options is selected MDaemon will create new mail session windows that are completely hidden from view.

In a default window

If this option is selected MDaemon will create new mail session windows using the default settings provided by Windows which relate to size and visibility.


Servers

Server Related Options

SMTP system uses ESMTP whenever possible

Select this switch if you wish to enable support for extended SMTP commands.

Honor ESMTP VRFY commands

Click this switch to allow ESMTP VRFY commands.

Honor ESMTP EXPN commands.

Click this checkbox if you want MDaemon to honor ESMTP EXPN commands.

SMTP server refuses mail which uses a NULL return path (RFC no-no)

Click this checkbox if you want the SMTP server to refuse mail that uses a NULL return path.

Remember states of SMTP/POP/IMAP servers across server reboots

If this control is enabled, MDaemon will ensure that the state of its servers (enabled or disabled) remains the same after a reboot.

POP/IMAP servers honor APOP/CRAM-MD5 authentication methods

Enable this control if you want MDaemon’s POP and IMAP servers to honor the APOP and CRAM-MD5 methods of authentication. These methods provide extra security by making it possible for users to be authenticated without sending clear text passwords.

POP DELE command immediately removes messages from mailbox

Click this switch and MDaemon will delete immediately messages that a user has retrieved even if the POP session does not complete properly.

Hide ESMTP SIZE command parameter

Click this checkbox if you want the ESMTP SIZE command parameter to be hidden.

Return gateway mail to gateway dir after failed ETRN delivery attempt

Click this checkbox if you want MDaemon to return a gateway domain’s email to the gateway’s directory if it fails to be delivered during an ETRN delivery attempt.

SMTP sends 552 response to over quota condition (normally 452)

Enabling this control will cause a 552 response ("Requested mail action aborted: exceeded storage allocation") when delivery is attempted to a recipient whose account exceeds its quota. Normally there would be a 452 response ("Requested action not taken: insufficient system storage").

POP/IMAP servers always accept connections from IP [IP address]

The POP and IMAP servers will always accept connections from the IP Address entered into this field regardless of screening and shielding settings.

RAW server converts this many messages per interval

Use this control if you wish to limit the number of RAW messages that may be converted during any given mail processing interval. If the limit is reached then MDaemon will wait until the next processing interval before converting further messages.

Allow this many RCPT commands per message (RFC says 100)

Use this control if you wish to limit the number of RCPT commands that can be sent per message.

Data Transfer Limits

Don’t accept SMTP delivered messages larger than XX KB.

Setting a value here will prevent MDaemon from accepting or processing SMTP delivered mail which exceeds a certain fixed size.  When this feature is active MDaemon will attempt to use the ESMTP SIZE command specified in RFC-1870.  If the sending agent supports this SMTP extension then MDaemon will determine the message size prior to its actual delivery and will refuse the message instantly.  If the sending agent does not support this SMTP extension then MDaemon will have to begin acceptance of the message, track its size periodically during transfer, and finally refuse to deliver the message once the transaction has completed.

Kill the socket connection if transmission of data exceeds XX KB

If the transmission of data during an MDaemon connection exceeds this threshold, MDaemon will close the connection.


Headers

Message Header Processing

Force "Date" header in all messages

When a message is encountered which doesn’t have a "Date:" header, MDaemon will create one and add it to the message file if this switch is selected. It will be the date on which MDaemon first receives the message, not when it was created by a mail client.  There are some mail clients that do not create this header, and since some mail servers refuse to honor such messages this feature will enable them to be delivered.

Force "Reply-To" header in all messages

When a message is encountered which doesn’t have a "Reply-To" header, MDaemon will create and add one to the message file using the address found in the "From" header.  If a "Reply-To" header is present but empty, MDaemon will create the header like this: Reply-To: "". This fixes problems for some mail clients.

Force "Message-ID" header in all messages

When a message is encountered which doesn’t have a "Message-ID" header, MDaemon will create one at random and insert it into the message.

Honor "Return-Receipt-To" headers

This switch determines how MDaemon will behave when faced with a request for deliver confirmation from an incoming message.  If set, a confirmation message will be dispatched to the sender of the triggering message.  Otherwise such requests are ignored.

Add "Precedence: bulk" header to system generated mail

Click this option if you want all system generated messages (welcome messages, warnings, "could not deliver" messages, and so on) to have a "Precedence: bulk" header inserted.

Strip X-type headers from local messages

MDaemon uses many server specific headers called X-Type headers in order to route mail and perform various MDaemon specific functions.  This switch will force MD to clean up after itself and remove these headers from messages as they are moved into local mailboxes.

Hide local IPs when processing message headers

Click this option to prevent MDaemon from placing local IP addresses into message headers when it processes mail.

Authenticate list posters using "From:" header

Usually senders to private lists are checked using the MAIL FROM value passed during the SMTP session. If you would rather have your system use the message’s "FROM:" header then enable this switch.

Add this header and value to every list message [header]

If you wish to add a static header/value combination (such as "Precedence: bulk") to all list messages, then specify it here.


Fixes

Various Fixes and Work Arounds

Fix MS Internet mail build 1160+ bug

This switch has been added in an attempt to deal with the Microsoft Internet Mail problem of messages not appearing on the display after they are downloaded. With this switch turned on, MDaemon will strip consecutive CRLFCRLF sequences from the end of the message body. Three sets of CRLF pairs at the tail end of a message file is the cause of the Microsoft problem.

Fix MS Outlook missing "from" field bug

Some versions of Microsoft Outlook fail to create a FROM header when you compose a message. The FROM field information is instead placed in the SENDER field. This can confuse downstream mail servers as well as the recipient of your message. Select this switch and MDaemon will create the missing FROM field using the address found in the SENDER field.

Allow for SUN OS compatibility

Allow Nulls and LF.LF for end of message mark in addition to the normal CRLF.CRLF sequence.

Use safe UIDL hash method

When you have configured MDaemon to leave messages on the host server after it has downloaded them, a UIDL hash method is used to identify those already retrieved messages. Previously MDaemon’s UIDL hash method was not compatible with Windows’ treatment of Daylight Savings Time. All stored messages would appear to be new and thus downloaded again a single time. Enable this feature if you want to switch to the new "safe" UIDL hash method that is unaffected by Daylight Savings Time.

Note:
Switching to the new hash method will cause all stored messages to appear to be new a single time and thus downloaded again. Thereafter messages will be unaffected by Daylight Savings Time.


System

System Properties

Pre-process mailing list mail

When a message arrives for a mailing list that should have been directed to the system address, MDaemon will reject it when this control is enabled. For example, a user may join or leave a list by placing the Subscribe or Unsubscribe command at the beginning of an email message and sending it to the system address. Oftentimes users erroneously try to send these messages to the list itself. Enabling this control will prevent these messages from being posted to the list.

Move account mail to new directories when domain names change

If this checkbox is enabled when you rename a domain, that domain’s existing account mail will be moved to directories with the new name. Otherwise, MDaemon will continue to use the old mail directory names.

MDaemon system account email address [address]

This is the email address from which system generated messages will come. Subscription confirmations, "Could not deliver" messages, various notification messages, and so on are all system messages.

Default attachment extension

System generated messages will be created using this extension. This will also be the extension assigned to attachments included with system generated messages. For example, if MDaemon generates a warning message to the postmaster about a specific message it will attach that message with an extension of ".md".

Default logon delimiter character (string of 10 characters max)

When using an email address as the account logon parameter, this character or string of characters can be used as an alternative to "@". This may be necessary for some users that have email clients which do not support "@" in the logon field. For example, if you used "$" in this field then users could login using "user@domain.com" or "user$domain.com".

CHAR-SET value for auto-generated messages

Specify the character set that you wish to be used for auto-generated messages. The default setting is US-ASCII.

Second machine IP for dual socket binding

If you want the Primary domain to be bound to an additional IP address then include it here.


  Disk

Disk Monitor Properties

Enable disk space checking engine

Activate this checkbox if you want MDaemon to monitor the amount of disk space that is available on the drive where the MDAEMON.EXE is located.

Low Disk Space Warning

Send warning to [user or address] when free disk space falls below [xx] KB

By using this option you can configure MDaemon to send a notification message to the user or address of your choice when disk space drops below a certain level.

Automatic shutdown

MDaemon will automatically disable TCP/IP services if free disk space falls below [xx] KB

Enable this feature if you want MDaemon to disable TCP/IP Services if free disk space drops to a certain level.


Misc

Enable disk checking for waiting message counts

This switch governs whether MDaemon will check the disk to count waiting messages in the mail queues.  Doing so can cause excessive disk spin over the long term.

Process/check for mail when server is first loaded

If selected MDaemon will create a mail processing event when it first loads.

Use strict quotas (count subdirectories and hidden files)

When this box is checked, all files and subdirectories will apply toward any size or message number limitations placed on a user’s account mailbox. Otherwise, only actual message files will count toward these limitations.

Do not send welcome message to new accounts

By default, MDaemon will generate a Welcome message based upon the welcome.dat file and distribute it to new users when their account is created. Enable this control if you want to prevent the message from being generated.

Create "Everyone" mailing lists

Clear this checkbox if you do not wish "Everyone" mailing lists to be created and maintained for your domains. Maintaining mailing lists of every user on every MDaemon domain could be a potential waste of resources if the lists are never used or are for very large numbers of users. Clear this checkbox if you do not want MDaemon create these lists.

Honor requests for account information

Provides the user list when requested via EXPN or LISTS commands.

Auto responders are triggered by local as well as remote mail traffic

Sometimes it is advantageous to disable the auto-response engine for local mail traffic.

Apply content filter rules to list mail before individual messages for list members are cracked

When the MDaemon will crack list mail option is chosen on the Routing tab of the mailing list editor, enabling this control will cause the content filter rules to be applied to list messages before they are cracked and distributed to list members.

POP, IMAP, WorldClient passwords are case sensitive

POP, IMAP, and WorldClient passwords will be case-sensitive when this control is checked.

Deleting users via MDConfig also removes their mail directory

Click this checkbox if you want users’ mail directories to be deleted when their account is deleted via MDConfig. Otherwise, their account will be deleted but their messages and directories will remain.

"Subject" header for new account welcome messages

When MDaemon sends the "Welcome" message to new accounts, this text will appear as the message’s "Subject" header. The welcome message is constructed from the Welcome.dat file contained in the …/MDaemon/app/ directory, and this subject header control may contain any macros permitted in auto response scripts.


Account Manager

To better manage the selection, addition, deletion, or modification of your accounts, MDaemon Version 3 contains the new Account Manager (Accounts|Account Manager…). This dialog provides much better access to account information and can be used to sort accounts by domain, name, or mail directory.

Account List

Above the Account List you will see two statistics regarding the list. The first number is the total number of MDaemon user accounts that currently exist on your system. The second number is the number of those accounts currently displayed in the Account List. Which accounts that will be displayed is contingent upon what you have chosen in the Show Only Accounts From This Domain control. If you have selected "All Domains" then all of your MDaemon accounts will be displayed in the list.

Each Account List entry lists the Domain to which it belongs, the Mailbox, the "Real Name" of the account holder, and the Mail Directory in which the account’s messages are stored. This list can be sorted in ascending and descending order by whichever column that you prefer. Click any column heading to sort the list in ascending order by that column. Click the column again to sort it in descending order.

Note
By default, only 500 accounts at a time will be displayed in this list. If you want to see more accounts from the currently selected domain (or All Domains, if you have selected that option) then you must click the "Show More Accounts" button to display the next 500. If you want to be able to display more than 500 accounts at a time then open the MDaemon.ini file and change the MaxAccountManagerEntries=500 key to whatever value that you prefer.

Show only accounts from this domain

Choose "All Domains" from this drop-down list box to display all MDaemon accounts. Choose a specific domain to show only that domain’s accounts.

New

Click this button to open the Account Editor in order to create a new account.

Edit

Select an account from the Account List and then click this button to open it in the account editor.

Delete

Select an account from the Account List and then click this button to delete it. You will be asked to confirm you decision to delete the account before MDaemon will proceed.

Show more accounts

The account list will only display 500 accounts at a time. If there are more than 500 accounts in the domain that you have chosen then click this button to display the next 500. See the note above for instructions on how to increase the maximum number of accounts that may be displayed.

Top

Click this button to quickly move to the top of the Account List.

Import

This opens the OPEN dialog from which you can choose a text file to import accounts from. This button is identical to the Accounts|Import|From a text file… menu selection.

New account defaults

Click this button to open New Account Defaults dialog.

See:

New Account Defaults

Account Editor

Creation an MDaemon User Account

Editing an MDaemon User Account


 Editing an MDaemon User Account

In addition to the using the Edit button on the Account Manager, you can also open an account for editing by selecting its entry on the Select Account dialog. You can open this dialog by clicking the Accounts|Edit Account… menu selection. Accounts are listed in alphabetical order by Mailbox followed by the account holder’s "Real Name" in parentheses. Double click an entry to open it in the Account Editor, or select the entry and then click Ok. You can quickly jump to an entry in this list by typing the first few letters of the Mailbox.

This list of accounts is costly in terms of system resources required to generate it. Consequently, it is impractical for use with large user lists. By default, this selection box is not available when account lists exceed 250 members. You can configure the threshold and raise it to a higher value by editing the following key in the MDaemon.ini file:

[Special]

MaxAccountsInListBox=250

Setting this value to 0 will make this selection box always available.


Creating an MDaemon User Account

Create a new MDaemon user account by clicking New on the Account Manager or Accounts|New Account… on the Message Router. This will open the Account Editor for configuring the account. You can designate default settings for new accounts by using the New Account Defaults dialog. In Addition, if you are synchronizing accounts between MDaemon and WorldClient Pro, creating an account in WorldClient Pro will cause an identical account to be created in MDaemon.


 Account Defaults

Account Defaults contains various account setting controls and template strings. Templates make it possible for you to specify default values for common user account components. The various string values associated with accounts such as Mailbox and POP Password can be constructed using a variety of special macros that will be replaced by actual values when an account is being created or imported. Use of these templates can greatly simplify and automate new account management.

Default Account Settings

Mailbox

Use this field to specify a default Mailbox name template for new accounts. In addition to being the Mailbox, this value will be the name passed in the USER POP command, which enables access to a mailbox from a remote location or POP aware mail clients. See Macros below for a list of the Macros that can be used in this template string.

Password

This template specifies a default POP Password for new accounts. This is the value passed in the PASS POP command, which allows access to a mailbox from a remote location or POP aware mail clients. See Template Macros below for a list of the Macros that can be used in this template string.

Mail directory

Use this field to specify a default mail directory for new accounts. These directories are where the actual mail files delivered to the mailbox will be stored. Care must be taken to ensure that once expanded, the template provided here will form a true DOS™ path.

Default Account Options

These switches are used for designating default values for various account settings. For more information on these switches, see Account Editor

Default Quota Settings

These switches are used for designating default values for a new account’s quota settings.  For more information on these switches, see Account Editor

Apply Installation Defaults to All Template Values

Clicking this button will cause the controls contained on this tab to be reset to their original installation default settings.

Template Macros

Below is a quick reference to the macros available for automating your account setup.

$DOMAIN$	This variable will resolve to the domain name selected for the account.
$DOMAINIP$	This variable will resolve to the IP associated with the domain currently selected for the account.
$USERNAME$	This variable resolves to the full first and last name of the account holder.  This field is equivalent to "$USERFIRSTNAME$ $USERLASTNAME$"
$USERFIRSTNAME$	This variable resolves to the first name of the account holder.
$USERLASTNAME$	This variable resolves to the last name of the account holder.
$USERFIRSTINITIAL$	This variable resolves to the first letter of the account holder’s first name.
$USERLASTINITIAL$	This variable resolves to the first letter of the account holder’s last name.
$MAILBOX$	This variable resolves to the mailbox name of the current account. The value will also used as the POP user name used in POP3 mail sessions.  This is the value expected in the USER command during POP session handshaking.


 Web Access Defaults

The Web Access Defaults dialog is used for designating the default access rights that new accounts will have for WorldClient and WebConfig. You can designate whether or not accounts will be able to access their email via WorldClient and whether or not users will be able to configure their accounts via WebConfig. In addition, if you are granting access to WebConfig, you can control which settings that accounts will be allowed to edit.

Web-based Mail Access Defaults

Account can access email via WorldClient Standard

Enable this checkbox if you would like new accounts to be able to access the WorldClient Standard server, which enables them to check their email using a web browser.

Web-based Remote Configuration Defaults

Accounts can modify its own settings via  WebConfig

Enable this feature if you want to grant MDaemon users permission to modify their account settings via WebConfig. They will only be able to edit those settings that you designate on this dialog.

When this feature is enabled, and the WebConfig server is set to Active on the Message Router, users will be able to log on to WebConfig using their browser by pointing it to http://mdaemonsdomain.com:Port. They will first be presented with a logon screen and then a screen that contains the settings that they have been given permission to edit.  All they need to do is edit whatever settings they choose and then click the Save Changes button. They can then close their browser; there is no need to logoff or do anything further.

Accounts that have been given administrative permission (designated on the individual account’s Web tab) will see a different screen after they log on to WebConfig.

By default, accounts can do the following via WebConfig:

Edit real name

Enabling this feature will allow users to modify their Real Name setting.

Edit password

Click this checkbox if you wish to allow users to modify their POP Password.

Edit mail directory location

This control is used to give users permission to modify the location of their Message Directory.

Note
You should exercise caution in granting this permission to users. Giving users the ability to change their mail directory could effectively give them access to any directory on your system.

Edit forwarding address

When this feature is enabled users will be able to modify their forwarding address settings.

Edit advanced forwarding

When this feature is enabled users will be able to modify their Advanced Forwarding Options.

Edit encrypt mail setting

This feature allows users to control whether or not mail messages of 4096 bytes or less will be stored in their mailbox in an encrypted state.

Edit IMAP rules (PRO version only)

Use this control to enable users to create and manage their own IMAP Mail Rules. This feature is only available in MDaemon PRO.

Edit EVERYONE list setting

This feature allows users to control whether or not they will be included on MDaemon’s EVERYONE Mailing List.

Edit intranet only setting

Click this checkbox to restrict accounts to sending local mail only.

Edit quota settings

Click this checkbox if you wish to allow accounts to modify their quota settings.

Edit MultiPOP settings

Click this switch if you wish users to be able to enable and disable MultiPOP collection.

Note
This permission doesn’t grant users the ability to create, delete, or edit MultiPOP entries in any way. MultiPOP entries must be created by the administrator using the MDaemon interface. This feature is for allowing users to control whether or not MultiPOP Mail Collection for their account is turned on.

Edit autoresponder settings

Click this checkbox if you want users to be able to add, edit, or delete AutoResponders for their account.

Edit allow changes via email

Click this checkbox if you wish to allow users to modify their Account Settings via specially formatted email messages.

Apply these defaults to all accounts now

Click this button to cause these default settings to be applied to all MDaemon accounts.  Any alternate settings that have been specified under individual accounts will be lost; the Web settings of all current MDaemon users will be changed to the settings specified here.


Account Editor

The Account Editor contains all settings specific to MDaemon accounts. It is used for creating new user accounts and for editing existing accounts. When creating a new account, most fields will be automatically filled in while typing the Real Name of the user. This auto-generated information is based on the templates and settings found in New Account Defaults.

The Account Editor’s ten tabs are:

Account

Mailbox

Forwarding

Options

Quotas

Web

MultiPOP

See:

Account Manager

New Account Defaults.

Creation an MDaemon User Account

Editing an MDaemon User Account


LDAP Address Book Support

MDaemon v3.5 supports Lightweight Directory Access Protocol (LDAP) address book functionality. Click Setup| LDAP Options… to open the LDAP Options dialog used for configuring MDaemon to keep your LDAP server up to date on all of its user accounts. This makes it possible for users with mail clients that support LDAP to "share" a global address book that will contain entries for all of your MDaemon users as well as any other contacts that you include.

LDAP Options

LDAP Options

Mirror account email addresses and full names to LDAP address book

Enable this control if you want MDaemon to keep your LDAP server up to date on all of your users’ names and email addresses.

LDAP Server Properties

Host name or IP

Enter the host name or IP address of your LDAP server here.

Port

Specify the port that your LDAP server is monitoring. MDaemon will use this port when posting account information to it.

Base entry DN

Enter the distinguished name of the base entry (root DN) that will be used in all of your MDaemon user entries.

RDN filter

The relative distinguished name (RDN) is the leftmost component in each entry’s distinguished name (DN). For all peer entries (those sharing a common immediate parent) the RDN must be unique, therefore we suggest using the email address of each user as their RDN to avoid possible conflicts. Using the $EMAIL$ macro as the value of the attribute that you specify in this control will cause it to be replaced by the user’s email address when their LDAP entry is created. The user’s DN will be comprised of the RDN plus the Base entry DN above.

Bind DN

Enter the DN of the entry to which you have granted administrative access to your LDAP server so that MDaemon can add and modify your MDaemon user entries. This is the DN used for authentication in the bind operation.

Bind Password

This password will be passed to your LDAP server along with the Bind DN value for authentication.

Object class

Specify the object class to which each MDaemon user’s entry must belong. Each entry will contain the objectclass= attribute with this as its value.

Configure

Click this button to open the LDAP.dat configuration file in a text editor. It is used for designating the LDAP attribute names that will correspond to each MDaemon account field.


SLAPD Server

SLAPD Properties

Start SLAPD when MDaemon starts

Click this checkbox if you want to launch your LDAP server when MDaemon starts. At startup MDaemon will run the program specified in the SLAPD command line field.

SLAPD command line

If you want MDaemon to launch your LDAP server at startup then type its startup command line into this field.

Hide the SLAPD window

Click this checkbox if you want launched program’s window to be hidden.

Pause [xx] seconds to allow SLAPD to completely load

This is the number of seconds that MDaemon will pause its operations after launching the program specified in the command line. This pause is to give the program time to fully load before MDaemon begins processing messages.


 Account

Personal Information

Real name

Enter the user’s first and last name here. When setting up a new mail account, the templates are reapplied each time the value in this field is changed. Real names cannot contain "!" or "|".

POP/IMAP Account Information

Mailbox name

This field specifies a unique name for the mailbox, and is also used as the account’s POP/IMAP login. In addition, the Mailbox must be unique and cannot contain spaces. After entering the name of the mailbox, click the drop-down list box and choose the domain to which this account’s mailbox will apply. MDaemon’s Primary Domain will appear in this control by default. Mailbox names cannot contain "!" or "|".

Allow this account to be accessed with POP/IMAP mail clients

This switch governs whether or not POP and IMAP access to the mailbox is allowed.

Account password

Enter an account password in this field. Below this field you will see a short statement that will tell you whether or not Dynamic NT Authentication is being used for this account.

Note
You should always provide Account Password information even if you do not wish to allow POP/IMAP access to the mail account. If you wish to disallow access then use the Allow This Account To Be Accessed… switch rather than leaving the Account Password field blank. In addition to POP session verification, user and password values are used to allow remote account manipulation and remote file retrieval.

Aliases

Aliases

Click this button to open the Alias Editor, which will have the current account displayed and any aliases assigned to the account listed. You can use this dialog to edit previously configured aliases or create new ones.


 Mailbox

Mail Storage Information

Message directory

Enter the directory where inbound mail messages destined for this account’s mailbox should be placed.

Storage Format

Storage format

This window allows you to attach an MBF to the mailbox message directory.  MBF files provide a method of mail system compatibility which may be useful in integrating your existing mail system with MDaemon Server v3.  For a complete discussion of MBF files and how to construct them see Creating and using MBF files .

Edit MBF

This button will allow easy editing of the account’s MBF file.

Advanced Options

Enable automatic extraction of MIME encoded attachments

If set, this switch causes MDaemon Server v3 to automatically extract any Base64  MIME embedded file attachments found within incoming mail messages.  Extracted files are removed from the incoming mail message, decoded, and placed in the account’s File Directory.  A notice is placed within the textual portion of the mail message in place of the encoded data which states where the file was placed and what the file name is.  This feature is extremely useful for mail transport systems and clients which do not have built in MIME capability or which require encoded parcels to be extracted and placed in separate directories from the textual portions of the mail message before being submitted into the mail stream.

User’s who wish to access their accounts through POP agents such as Eudora or the Windows Exchange client may wish this option to be turned off (not set) as more powerful email client software can properly handle MIME Base64 encoded attachments.


 Forwarding

Mail Forwarding Options

This account is currently forwarding mail

This switch governs whether or not mail will be forwarded to the address specified in the Forwarding Address field.

Forwarding address

This field allows you to specify an address where copies of all inbound mail messages destined for this account will be automatically forwarded once they arrive at the server and are delivered to the account’s local mail directory.  A copy of each new message arriving at the server will be automatically generated and forwarded to the address specified in this field provided the This Account Is Currently Forwarding Mail switch is selected.

Retain a local copy of forwarded mail

If the account is forwarding mail to another address it may not be necessary for MDaemon to retain a copy of the message in the users local mailbox.  This switch governs that action.

Advanced Forwarding Options

Forward the message to this host

If a mail host is specified here the forwarded message will be delivered to it rather than to the domain specified by the value found in the Forwarding Address field.

Use this address in SMTP envelope

If an address is specified here, this address will be used in the SMTP "Mail From:" statement used during the session handshaking with the accepting host.  Normally, the sender of the message is used in this portion of the SMTP envelope. If you require an empty SMTP "Mail From:" command (looks like this: MAIL FROM <>) then enter "[trash]" into this control.

Use this TCP port

MDaemon will send this message on the TCP port specified here rather than the default SMTP outbound port.


 Options

Account Options

Hide account from the ‘EVERYONE’ list, LDAP address book, and VRFY results

MDaemon automatically creates and maintains a mailing list called Everyone which can be used to address each account on the server. By default MDaemon will include all accounts when it constructs the Everyone mailing list. Uncheck this switch if you want the account to be private and hidden from other users. This will also hide the account from the LDAP address book and VRFY results.

Store mail messages in an encrypted state

If selected, MDaemon will store mail for this account in an encrypted state.  The messages will not be directly readable while in this state and should provide a very good level of protection.  MDaemon will decrypt the message when it is transmitted via POP to the account holder but while stored on disk this account’s message files will be encrypted.

Allow changes to account settings via email messages

This switch determines whether the user has access to account variables through remote email messages.  This feature allows the user to perform common account maintenance such as changing passwords or mail directories by sending specially formatted mail messages to the server.  For a complete discussion on remote account manipulation see Remote Server Control Via Email .

This account is restricted to sending and receiving local mail only

This switch may be used to limit an account so that it can only send local (Intranet) mail.  Local mail includes LAN and Gateway Domain mail as well.  A corresponding switch in the Account Template Editor lets you choose to set this as a default for creating new accounts if you so desire.


 Quotas

Quota Options

This account must observe these quota settings

Here you can specify the account’s maximum number of allowable messages and the maximum amount of disk space (in kilobytes) that the account can consume (this includes any decoded file attachments in the account’s File Directory). If a mail delivery to the account is attempted which would exceed the maximum messages limit or the maximum disk space allocated then the message is forwarded to the postmaster along with an appropriate warning. If a MultiPOP collection would exceed the account’s maximum a similar warning is issued and the account’s MultiPOP entries are automatically switched off (but not removed from the database).


 Web

Web-based Mail Access

Account can access  email via WorldClient Standard

Enable this checkbox if you would the account to be able to access the WorldClient Standard server, which enables them to check their email using a web browser.

Web-based Remote Configuration Permissions

Account can modify its own settings via the WebConfig

Enable this feature if you wish to grant the MDaemon user permission to modify their account settings via WebConfig.  They will only be able to edit those settings that you enable below.

When this feature is enabled, and the WebConfig server is set to Active on the Message Router, user will be able to log on to WebConfig using their browser by pointing it to http://mdaemonsdomain.com:Port.  They will first be presented with a logon screen and then a screen that contains the settings that they have been given permission to edit.  All they need to do is edit whatever settings they choose and then click the Save Changes button.  They can then close their browser; there is no need to logoff or do anything further.

If the user has been given administrative permission (by enabling This Account Can Edit Other Users And MDaemon Via The Web) they will see a different screen after they log on to WebConfig.

See WebConfig.

This account has administrator level access to WebConfig

Enable this checkbox to grant the user administrative access to WebConfig. This will give the user complete access to MDaemon’s files and options via the web.

See WebConfig.

Edit real name

Enabling this feature will allow the user to modify their Real Name setting.

Edit password

Click this checkbox if you wish to allow the user to modify their Account Password.

Edit mail directory location

This control is used to give the user permission to modify their Message Directory location.

• Caution!
You should exercise caution in granting this permission to users.  Giving users the ability to change their mail directory could effectively give them access to any directory on your system.

Edit forwarding address

When this feature is enabled, the user will be able to modify their forwarding address settings.

Edit advanced forwarding

When this feature is enabled, the user will be able to modify their Advanced Forwarding Options.

Edit encrypt mail setting

This feature allows the user to control whether or not mail messages of 4096 bytes or less will be stored in their mailbox in an encrypted state.

Edit IMAP rules (PRO version only)

Use this control to enable users to create and manage their own IMAP Mail Rules. This feature is only available in MDaemon PRO.

Edit EVERYONE list setting

This feature allows the user to control whether or not they will be included on MDaemon’s EVERYONE Mailing List.

Edit intranet only setting

Click this checkbox to restrict the account to sending local mail only.

Edit quota settings

Click this checkbox if you wish to allow the account to modify their quota settings.

Edit MultiPOP settings

Click this switch if you wish the user to be able to enable and disable MultiPOP collection.

This control doesn’t grant the user the ability to create, delete, or edit MultiPOP entries in any way.  MultiPOP entries must be created by the administrator using the MDaemon interface.  This feature is for allowing users to control whether or not MultiPOP Mail Collection for their account is turned on.

Edit autoresponder settings

Click this checkbox if you want the user to be able to add, edit, or delete AutoResponders for their account.

Edit allow changes via email

Click this checkbox if you wish to allow the user to modify their Account Settings via specially formatted email messages.

Apply defaults

Click this button to cause the default settings designated on the Web Access Defaults dialog to be applied to this MDaemon account. Any alternate settings that have been specified on this individual’s account will be replaced by the Web Access Defaults settings.


Auto Responders

Autoresponse Event

Enable an auto responder for this account

Enable this control to activate an auto responder for the account. For more information on auto responders see: Auto Responders and MBF Files

Use this auto response script

This field specifies the full path and filename of the response file (*.RSP) that will be processed and dispatched to the message sender. This file will first be passed through the filtering mechanism associated with MBF files. Any template string available for use in an MBF file will also be available for use in an auto-response file.

Do not send auto response if message is from one of these addresses

Here you can list addresses that you wish to be excluded from responses initiated by this Auto Responder.

Note:
Occasionally Auto Response messages may be sent to an address that returns an Auto Response of its own. This can create a "ping-pong" effect causing messages to be continually passed back and forth between the two servers.  You can use this feature to prevent an MDaemon Auto Responder from sending responses to one or more of these addresses by entering them here.

Del

Click this button to delete selected entries from the list of excluded addresses.

New excluded address—wildcards okay

If you wish to add an address to the list of excluded addresses enter it here and then click the Add button.

Run a Program

Run this program

This field specifies the full path and filename to a program that will be launched when new mail arrives at the specified mailbox. Care must be taken to ensure that this process terminates properly and can run unattended. Optional command line parameters can be entered immediately following the executable path if desired.

Pass message to process

Select this option and the process specified in the Run This Program field will be passed the name of the triggering message as the first available command line parameter. Note that by the time the message name is passed to the specified process the account’s MBF file will already have been applied. This is useful in that applying an MBF can reformat the message into a consistent structure regardless of the source of the original message. When the auto responder is setup on an account which is forwarding mail to another location and not retaining a local copy in its own mailbox (see Forwarding) then this function will be disabled.

Note
By default, MDaemon will place the name of the message file as the last parameter on the command line.  You can override this behavior by using the $MESSAGE$ macro. Use this macro in place of where the message file name should be placed.  This allows more flexibility in the use of this feature since a complex command line such as this will be possible:  logmail /e /j /message=$MESSAGE$ /q

Advanced Options

Add sender to this mailing list

If a mailing list is entered in this field then the sender of the mail message will be automatically joined to that mailing list. This is a very handy feature for building automatic lists.

Remove sender from this mailing list

If a mailing list is entered in this field then the sender of the mail message will be automatically removed from the specified mailing list.

TIP
Auto-Response events are always honored when the triggering message is from a remote source. For messages originating locally, whether or not an Auto Responder will but triggered is contingent upon a setting on the Miscellaneous Options dialog. The control is: Auto Responders are triggered by Local as well as Remote Traffic. Enable the control if you want Local mail to trigger an auto response.


IMAP Mail Rules

New to MDaemon 3.5 is the ability for IMAP users to have their mail routed automatically to specific folders directly on the server. Similar to the Content Filters, MDaemon will examine the headers of each message and then compare them to rules. When a message for the account holder matches one of their rules, MDaemon will move it to the folder specified in that rule. This method is much more efficient (for both the client and server) than attempting to filter the messages at the client, and since some IMAP clients do not even support message rules or filtering, IMAP Mail Rules provides this functionality to them.

IMAP Mail rules and messages folders can be created directly on the server via the IMAP Mail Rules tab of the Account Editor. They can also be created by the users themselves via specially formatted email messages. Support for managing IMAP Mail Rules has also been added to WebConfig. By simply logging in to WebConfig with their browser they can manage their own account rules and settings that you have given them permission to manage. Thus, by using WebConfig you can give your users total control over their own rules and avoid having to manage those functions for them.

Existing IMAP Mail Rules

This box displays the list of all rules that have been created for the user’s account. Rules are processed in the order in which they are listed until a match is found. Therefore, as soon as a message matches one of the rules it will be moved to the folder specified in that rule and then rule processing for that message will cease. Use the Up and Down buttons to move rules to different positions in the list.

Remove

Click a rule in the list and then click Remove to delete it from the list.

Clear all

Clicking this button will delete all of the user’s IMAP Mail Rules.

Up

Click a rule in the list and then click this button to move it to a higher position in the list.

Down

Click a rule in the list and then click this button to move it to a lower position in the list.

New IMAP Mail Rule

Use the controls in this section to create new IMAP Mail Rules for the users.

If the [message header] header

Type a message header into this box or choose one from the drop-down list. MDaemon will search this header in all of the account’s incoming messages for the text contained in the "This text" control below. Then, based upon the type of comparison being made, it will determine which messages should be moved to the rule’s specified folder.

Is equal to, is not equal to, contains, doesn’t contain

This is the type of comparison that will be made when a message’s headers are compared to this IMAP Mail Rule. MDaemon will search the specified header for the text contained in the "This text" field and then proceed based upon this control’s setting—does the header’s complete text match exactly, not match exactly, contain the text, or not contain it at all?

This text

Enter the text that you want MDaemon to search for when scanning the message header that you have specified for this rule.

Then move message to this folder

After specifying the various parameters for the rule, click the folder that you want messages matching it to be moved to and then click the Add rule button to create it.

New folder

Click this button to create a new folder. This will open the Create Folder dialog on which you will assign a name for the folder. If you want it to be a subfolder of an existing folder then choose the folder from the drop-down list.


 MultiPOP

The MultiPOP feature (located on the Account Editor) allows you to script an unlimited number of POP host/user/password combinations for collection of mail messages from multiple sources. This is useful for your users who have mail accounts on multiple servers but would prefer to collect and pool all their email together in one place. Before being placed in the user’s mailbox, MultiPOP collected mail is first placed in the local queue so that it can be processed like other mail having autoresponders and Content filters applied to it.

Note
This editor uses advanced common controls that were not present in the original shipping versions of Windows 95. If the MultiPOP editor will not retain your settings then you need to download and install the newer common controls DLL file from Microsoft (www.microsoft.com).

MultiPOP Mail Collection

Enable MultiPOP mail collection for this account

This switch must be enabled for MultiPOP processing to occur for the account.

Server

Enter the POP3 server from which you wish to collect mail.

Logon

Enter the POP3 USER or LOGON name that accesses the mail account on the specified server.

Password

Enter the POP3 password or APOP shared secret used for accessing the mail account on the specified server.

Use APOP (password field contains shared secret)

Click this checkbox is you want the MultiPOP entry to use the APOP method of authentication when retrieving mail from its corresponding host. Note: The Password control must contain the APOP shared secret when this feature is chosen.

Leave a copy of message on POP server

Click this checkbox if you want to leave a copy of collected messages on the server.  This is useful when you plan to retrieve these messages again at a later time from a different location.

Delete messages once [xx] or more have accumulated (0 = never)

This is the number of messages that MultiPOP will leave on the POP server before they will be deleted. When this number has accumulated, all stored messages will be deleted.  Enter "0" into this control if you do not wish to place a limit on the number of messages that may be stored.

Note
Some ISP’s limit the number of messages that may be stored so you should check with them about any restrictions that may apply to your account.

Don’t download messages larger than [xx] kb (0 = no limit)

Enter a value here if you wish to limit the size of messages that may be downloaded.

Remove

Click this button to remove the selected MultiPOP entries from the list.

Enable/disable

Clicking this button toggles the state of the selected MultiPOP entries.  This switch gives you control over whether MDaemon will collect mail for this entry or skip over it when it performs its MultiPOP processing.

Add

Press this button to add your values to the list of MultiPOP records.

Replace

When an entry is selected from the list it will be presented for editing. After making any desired changes, click this button to apply them.


Importing Accounts

MDaemon Server v3 supports multiple methods of importing user accounts. They may be imported from an NT SAM database, an SLMail user database, or directly from a text file. MDaemon’s import features are reached from the Accounts|Import menu selection.


Importing Accounts From a Text File

Click the Accounts|Import|From a Text File…menu selection to access this account generation feature. It can also be reached by clicking the Import button on the Account Manager. This is a simple method for importing and automatically generating mail accounts. MDaemon will read a text file and generate new mail accounts using just the first and last names of the user who will maintain the account. If you are careful to setup your account template strings properly (see New Account Defaults) you can generate unique accounts using only the first and last names of your users.

Each line of the text file that MDaemon reads must contain only a single name. A sample file would look something like this:

Frank Thomas

Jerry C Lovell

Johanne Gambleputty

First, middle, and last names are acceptable but do not use punctuation marks (periods, commas, and so on).

After running the import process, MDaemon will create TXIMPORT.LOG, detailing the import results and listing which accounts imported successfully and which failed. Typical reasons why an account might not be imported would include a conflict with an existing account’s mailbox, name, or directory information, a conflict with an existing alias to an account, or a conflict with a mailing list name.


Windows NT Security Account Integration

MDaemon supports Windows NT integration. This support consists of a Windows NT user database import engine, which can be reached through the MDaemon menu selection Accounts|Import|From NT SAM Database…. Additionally, support for dynamic authentication of users has been embedded into the MDaemon user management code. It is possible to specify an NT domain in an account’s password field and then MDaemon will dynamically authenticate such accounts in real-time, using the specified NT domain’s security system. Under such a scheme, changing the account’s password in the Windows NT User Manager will have the effect of automatically updating MDaemon. Therefore, your users will only have to remember one set of authentication credentials.  This also makes for very easy account setup for new installations.

• Important!

The security context of the account running MDaemon must have the SE_TCB_NAME privilege.  If the process is a service running in the Local System account, it will have this privilege by default. Otherwise, it must be set by the following procedure:

Run the "User Manager" (NT Administration tool) and select "User Rights" from the "Policies" menu.  NOTE:  You must select the "Show Advanced User Rights" check box to see the SE_TCB_NAME privilege. The correct privilege, SE_TCB_NAME, is labeled "To Act as Part of the Operating System".  Select this and "Add" this right to the account under which MDaemon operates. If you add this right you may need to restart MDaemon before it takes affect.

See Microsoft articles Q101366 and Q131144 for more detailed information.

NT to MDaemon Account Importer

NT Server Properties

PDC/BDC Machine name

This field allows you to specify the machine name from which MDaemon will read NT account database information.  You can specify \\<DEFAULT> and MDaemon will read data from the local machine.

Refresh

Click this button to refresh the NT Accounts listing.

NT Domain Name

Type the NT domain name from which you wish to import accounts.

MDaemon Domain Name

Choose from the drop-down list box the MDaemon domain into which the accounts will be imported.

Accounts to Import

NT accounts

This window contains a list of all the account names collected from the NT account database.

Selected accounts

This window contains all the account names that you have selected and wish to import.

>>

Click this button to move the highlighted account names from the "NT Accounts" window into the "Selected Accounts" window.

<<

Click this button to remove the highlighted entries from the "Selected Accounts" window.

Importing Options

Make account mailboxes equal to the NT account name

Click this switch to force each imported user’s NT account name to be used as their Mailbox value. With this method, you will not need to worry about setting up the correct New Account Template macros.

Use the account template to generate passwords

This switch causes MDaemon to generate passwords for imported accounts using the account template settings (see Account Defaults).

Set account passwords equal to account names

This switch causes MDaemon to use the account name as the account password.

Make every password equal to…

This switch allows you to specify a static password value that will be used by all imported accounts.

Authenticate passwords dynamically using NT database

This switch enables dynamic authentication of imported accounts.  Rather than specifying a password MDaemon will simply authenticate the mail client supplied USER and PASS values using the NT database in real-time.

Authenticate on this NT domain

Enter the name of the Windows NT domain that MDaemon will use when authenticating connections dynamically. This is not the machine name of the domain controller. It is the actual name of the NT Domain.

Note
When accounts are configured for dynamic authentication on an NT machine the name of the NT domain preceded by two backslash characters is used in the account’s PASSWORD field and is stored unencrypted within the USERLIST.DAT file. For example, if an account is configured for dynamic authentication on an NT domain called ALTN the account’s password field will contain the value \\ALTN. The two backslash characters preceding the domain name trigger MDaemon that the password field actually contains the name of an NT domain and that MDaemon should attempt to authenticate the USER and PASS values provided by the mail client using that domain’s account database. It is an error for a password to start with two backslash characters unless it is configured for dynamic authentication as described above. In other words, you can’t just have regular passwords that start with two backslashes. Passwords beginning with two backslashes are always assumed to be providing an NT domain name and not a password. It is perfectly acceptable to enter two backslashes and the NT domain name into an account’s password field using the regular Account Editor if necessary. The administrator need not restrict himself to using the importer in order to setup accounts for dynamic authentication.


Address Aliases

The Accounts|Address Aliases … menu selection is used to open the Alias Editor. The Alias Editor makes it possible for you to create "fictitious" mailbox names for your accounts or mailing lists, which is extremely useful when you want multiple mailbox names resolved to a single user account or list. For example, if Frank@altn.com handled all billing inquiries to your domain, but you wanted to tell everyone to send them to Billing@altn.com, then you could create an Address Alias so that messages addressed to Billing@altn.com would actually go to Frank@altn.com. Or, if you were hosting multiple domains and wanted all messages addressed to the Postmaster (regardless of the domain) to go to a single user, then you could create the alias "Postmaster@*=Henry@altn.com".

Because a "Postmaster" must exist at each Internet mail site, MDaemon will check your defined aliases at program startup and issue a warning if you have failed to create such an alias.


 Alias Editor

Define a New Alias

Address alias

Enter the email address for which you wish to create an alias. Wildcards of "?" and "*" are acceptable.

Actual address

Select an account from the drop-down list or type a new address or mailing list into this space. This is the actual address that will receive the message when it is addressed to a corresponding alias.

Add

Click the Add button to register the account alias request. The contents of the Address Alias and Actual Address fields will be combined and placed in the Current Aliases window.

It’s OK to relay mail for aliases that include foreign domains

Click this control if you want MDaemon to relay mail for Address Aliases regardless of your Relay Control settings.

Aliases are ignored if address matches an existing account or mailing list

Current Aliases

This window contains all current Address Aliases that you have created.

Remove

Click this button to remove a selected entry from the Current Aliases list.

Up

Aliases are processed in the order in which they are listed. You can move an Alias to a higher position in the list by selecting it and then clicking this button.

Down

Aliases are processed in the order in which they are listed. You can move an Alias to a lower position in the list by selecting it and then clicking this button.


Auto Responders and MBF Files

Auto responders are useful tools for automating events to be triggered by an incoming email message. One popular use for auto responders is to send back a user-defined message to any person who sends an email to a user who will be unable to read it due to a vacation, illness, or some other circumstance. Using the auto-response mechanisms provided with MDaemon Server v3 (located in Accounts|Auto Responders…), incoming mail can act as a trigger generating automated and personalized replies or as the cause of a server hosted process in which the message itself is passed as a command line parameter. Automated response message files (*.RSP files) can contain any template string available to an MBF file.

MBF or Mailbox Format Files are text files designed to allow cross compatibility with other email transport systems that can accept ASCII text files into their mail streams. MBF files are essentially templates that contain a set of special formatting macros that enable MDaemon to transform an RFC-822 message into a variety of other text-based formats. Using MBFs, MDaemon can be configured to automatically reformat incoming mail into specific alternatives on a per mailbox basis. When a message arrives for an MDaemon account, the account’s MBF file is used to reformat the incoming data before distributing it to the user.

See Creating Auto Response Scripts for more information on creating automated response message files to be used by Auto Responders.

See Creating and Using MBF Files for more information on MBF files.


 Auto Responders

Mailbox Listing

This control lists all available local mailboxes that can host an Auto Responder. Select a mailbox from this drop-down list and then fill in the desired auto response parameters to cause the Auto Responder to be triggered whenever a message arrives for the mailbox.

Remove

Clicking this button will remove any Auto Responder that is associated with the account selected in the Mailbox drop-down list box.

Auto Response Event

Use this auto response script

This field specifies the full path and filename of the response file (*.RSP) that will be processed and dispatched to the message sender. This file will first be passed through the filtering mechanism associated with MBF files. Any template string available for use in an MBF file will also be available for use in an auto-response file.

See:

Creating Auto Response Scripts

Creating and Using MBF Files

Do not send auto response if message is from one of these addresses

Here you can list addresses that you wish to be excluded from responses initiated by this Auto Responder.

Note
Occasionally Auto Response messages may be sent to an address that returns an Auto Response of its own. This can create a "ping-pong" effect causing messages to be continually passed back and forth between the two servers.  You can use this feature to prevent an MDaemon Auto Responder from sending responses to one or more of these addresses by entering them here.

Del

Click this button to delete selected entries from the list of excluded addresses.

Add

After entering an address in the New Excluded Address text box, click this button to add it to the list of excluded address.

New excluded address

If you wish to add an address to the list of excluded addresses enter it here and then click the Add button.

Run a Program

Run this program

This field specifies the full path and filename to a program that will be launched when new mail arrives at the specified mailbox. Care must be taken to ensure that this process terminates properly and can run unattended. Optional command line parameters can be entered immediately following the executable path if desired.

Pass message to process

Select this option and the process specified in the Run This Process field will be passed the name of the triggering message as the first available command line parameter. Note that by the time the message name is passed to the specified process the account’s MBF file will already have been applied. This is useful in that applying an MBF can reformat the message into a consistent structure regardless of the source of the original message. When the auto responder is setup on an account which is forwarding mail to another location and not retaining a local copy in its own mailbox (see Forwarding) then this function will be disabled.

Note
By default, MDaemon will place the name of the message file as the last parameter on the command line.  You can override this behavior by using the $MESSAGE$ macro. Use this macro in place of where the message file name should be placed.  This allows more flexibility in the use of this feature since a complex command line such as this will be possible:  logmail /e /j /message=$MESSAGE$ /q

Add sender to this mailing list

If a mailing list is entered in this field then the sender of the mail message will be automatically joined to that mailing list. This is a very handy feature for building automatic lists.

Remove sender from this mailing list

If a mailing list is entered in this field then the sender of the mail message will be automatically removed from the specified mailing list.

TIP
Auto-Response events are always honored when the triggering message is from a remote source. For messages originating locally, whether or not an Auto Responder will but triggered is contingent upon a setting on the Miscellaneous Options dialog. The control is: Auto Responders are triggered by Local as well as Remote Traffic. Enable the control if you want Local mail to trigger an auto response.


Creating Auto Response Scripts

Auto Response scripts define the messages that are returned as the result of an auto-response event. They are constructed the same as MBF files and can contain the same macros. However, several additional macros are provided which allow you to develop more powerful auto-response messages.

In addition to those template variables defined for MBF files, auto-response scripts can use any or all of the following macros, which override the values parsed from the original message:

%SetSender%

ex: %SetSender%=mailbox@host.org

MDaemon will treat this address as if it had sent the original message.

%SetRecipient%

ex: %SetRecipientr%=mailbox@host.org

Sets the address that will receive the auto-response message, regardless of the original sender.

%SetReplyTo%

ex: %SetReplyTo%=mailbox@host.org

Controls the value of the RFC-822 ReplyTo header

%SetActualTo%

ex: %SetActualTo%=mailbox@host.org

Changes who MDaemon thinks the "actual" recipient of the mail message should be.

%SetSubject%

ex: %SetSubject%=Subject Text

Replaces the value of the message’s subject.

%SetMessageId%

ex: %SetMessageId%=ID String

Changes the ID string of the message.

%SetPartBoundary%

ex: %SetPartBoundary%=Boundary String

Changes what MDaemon thinks is the part boundary.

%SetContentType%

ex: %SetContentType%=MIME type

Changes what MDaemon thinks is the content-type of the message.

%SetAttachment%

ex: %SetAttachment%=filespec

Forces MDaemon to attach the specified file to the newly generated auto-response message.


Auto Response Script Samples

A typical auto response script might be called VACATION.RSP and look like this:

Greetings $SENDER$

You’re message regarding ‘$SUBJECT$’ won’t be read by me because I’m on vacation so LEAVE ME ALONE!

Yours truly (yeah right!),

$RECIPIENT$

This is essentially the VACATION.RSP file that shipped with the first version of MDaemon. This example script uses macros developed for MBF files. Using the macros defined in the above table you can also control the headers which will be generated when this auto-response script is processed and mailed back to $SENDER$.

Let’s amend our old VACATION.RSP file to use some of the new macros:

Greetings $SENDER$

You’re message regarding ‘$SUBJECT$’ won’t be read by me because I’m on vacation so LEAVE ME ALONE!

Yours truly (yeah right!),

$RECIPIENT$

%SetSubject%=RE: $SUBJECT$

%SetAttachment%=c:\windows\bugoff.exe

The new message, which will be generated using this script as a template, will have a custom subject line and will have the specified file encoded as a MIME attachment.

The %SetSubject%=RE: $SUBJECT$ instruction is handled in this way:

1.	The $SUBJECT$ portion is expanded and replaced by the original message’s subject text. This makes the string equivalent to: %SetSubject%=RE: Original Subject Text.

2.	MDaemon replaces the original subject, which it has stored in its internal buffers, with this newly calculated one.  From then on any call to $SUBJECT$ or use of the subject field will return the new result.

Note the placement of the new macros - they are listed at the bottom of the response script. This is needed to avoid side effects. For example, if the %SetSubject% macro were placed before the $SUBJECT$ macro, which appears in the third line of the response script, the subject text will have been changed by the time the $SUBJECT$ macro is expanded. Therefore, instead of replacing $SUBJECT$ with the content of the original message’s "Subject:" header, it will be replaced with whatever you have set the value of %SetSubject% to be.


Creating and Using MBF Files

MBF or Mailbox Format Files are text files designed to allow cross compatibility with other email transport systems that can accept ASCII text files into their mail streams. MBF files are essentially templates that contain a set of special formatting macros that enable MDaemon to transform an RFC-822 message into a variety of other text-based formats. Using MBFs, MDaemon can be configured to automatically reformat incoming mail into specific alternatives on a per mailbox basis. When a message arrives for an MDaemon account, the account’s MBF file is used to reformat the incoming data before distributing it to the user.

MBFs are constructed as plain ASCII text files ending with the "*.MBF" file extension. They are scanned by the server for macros, which will be replaced by actual data from an incoming message. Lines beginning with the "#" character are ignored and are used for comments. Lines beginning with the ";" character are used to control the value of the reformatted message’s file name. When the MBF processor sees a line that begins with the ";" character it assumes that the text following this character will describe either the prefix or the extension which the processor should use when creating new files.

The syntax is:

; msg-prefix = SMF<cr><lf>

; msg-ext = <cr><lf>

If an MBF file contained lines as shown above, all reformatted mail messages created using the MBF file would take the form "SMFxxxx" where "xxxx" represents a random but unique identifier. The maximum length of the prefix component is four characters. The maximum extension that can be specified is three characters. Note that the above example purposely excludes an extension. These directives are optional and are not required to be present in any MBF file. However, their inclusion provides a means of directly manipulating message file names, which may be useful in integrating MDaemon Server v3 with an existing MTA. The default msg-prefix value is "MD" and the default msg-ext is "MSG".

Attachment file names can be similarly manipulated using the following syntax:

; attach-prefix = ATTH<cr><lf>

; attach-ext = ZIP<cr><lf>

This example would generate unique names for file attachments of the form "ATTHxxxx.ZIP" where "xxxx" represents a random yet unique identifier.  Like those for message file names, these directives are optional.

Note
These directives will have no effect on accounts that are not auto-extracting embedded attachments.

It is sometimes important to retain the original file’s extension while generating a unique file name for it. To accomplish this use the "; attach-ext = ???" syntax. This causes MDaemon to retain the attachment’s original extension. By default, auto-extracted attachments are decoded and stored in the user’s FILES directory under their original file names.


MBF Macros and Examples

The following is a list of all macros available for use when constructing an MBF file.  Following this list is a series of examples.

$HEADERS$	This macro will be replaced by all the original RFC-822 message headers - each separated by a CRLF delimiter.  Using this macro the MBF will obtain all the headers contained in the incoming message.  Text immediately preceding this macro will be duplicated at the start of each expanded line. For example: O-SMTP-HEADER: $HEADERS$  would place each of the original RFC-822 headers into the reformatted message each preceded by the text string "O-SMTP-HEADER:"
$HEADER:XX$	This macro will cause the value of the header specified in place of the "xx" to be expanded in the reformatted message.  For example:  If the original message has "TO:  joe@mdaemon.com" then the $HEADER:TO$ macro will expand to "joe@mdaemon.com".  If the original message has "Subject: This is the subject" then the $HEADER:SUBJECT$ macro would be replaced with the text "This is the subject"
$BODY$	This macro will be replaced by the entire message body.  In an attempt to preserve character sets for different languages, MDaemon will read the message body as stream binary data rather than pure text, thus allowing a  byte-for-byte copy of the message body.
$BODY-AS-TEXT$	This macro will be replaced by the entire message body as with the $BODY$ macro, except that MDaemon will read this as text rather than binary.  This may not be compatible with all charsets.  Text immediately preceding this template variable will be duplicated at the start of each expanded line; thus:  >>$BODY-AS-TEXT$ would place each of the original RFC-822 message lines into the reformatted message with the addition of the string text ">>" preceding them.  Text could also be added to the right of this macro.
$ATTACHMENTS$	This macro will be replaced by the entire list of all attached files extracted from the original message.  Text immediately preceding this template variable will be duplicated at the start of each expanded line. For example: FILE-LIST $ATTACHMENTS$ would place each of attachment file names into the reformatted message each preceded by the text string "FILE-LIST".
$ATTACHMENTCOUNT$	This macro will be replaced with an integer value equal to the number of attachments extracted from the original message.
$ATTACHMENT(X)$	This macro will be replaced with the attachment file name of the relative attachment number passed in the X parameter.  If the value in X is greater than the total number of attached files then the entire variable is removed and replaced with nothing.
$SENDER$	This macro resolves to the full address of the message originator and corresponds to the RFC-822 "To:" header.
$SENDERMAILBOX$	This macro resolves to the mailbox of the message originator.  The mailbox is the portion of the email address to the left of the "@" symbol.
$SENDERDOMAIN$	This macro resolves to the domain of the message originator.  This is the portion of the email address to the right of the "@" symbol.
$RECIPIENT$	This macro resolves to the full address of the message recipient.
$RECIPIENTMAILBOX$	This macro resolves to the mailbox of the message recipient.  The mailbox is the portion of the email address to the left of the "@" symbol.
$RECIPIENTDOMAIN$	This macro resolves to the domain of the message recipient.  The domain is the portion of the email address to the right of the "@" symbol.
$SUBJECT$	This macro resolves to the value of the RFC-822 "Subject" header.
$MESSAGEID$	This macro resolves to the value of the RFC-822 "Message-ID" header.
$CONTENTTYPE$	This macro resolves to the value of the RFC-822 "Content-Type" header.
$PARTBOUNDARY$	This macro resolves to the value of the MIME "Part-Boundary" value found in the RFC-822 "Content-Type" header for multipart messages.
$DATESTAMP$	This macro expands to an RFC-822 style date-time stamp line.
$ACTUALTO$	Some messages may contain an "ActualTo" field which generally represents the destination mailbox and host as it was entered by the original user prior to any reformatting or alias translation.
$ACTUALFROM$	Some messages may contain an "ActualFrom" field which generally represents the origination mailbox and host prior to any reformatting or alias translation.
$REPLYTO$	This macro resolves to the value found in the RFC-822 "ReplyTo" header.
$PRODUCTID$	This macro expands to the MDaemon Server v3 version information string.
\\XXX	This variable specifies an ASCII character code (000 - 255) that should be inserted into the MBF file.  This variable is always 5 characters long with the first two characters being "\\".  This instructs the server to expect a three digit number which represents an ASCII character code.  For example,  \\012 will place the ASCII character 12 (a formfeed character) into the MBF file.  The numeric value specified must be three characters long and padded with zeros if necessary.
Sample MBF file(s):

1) RFC-822.MBF

# RFC-822.mbf - mailbox format for standard RFC-822 translations

# version 1.1

$HEADERS$

X-MBF-FILE: MDaemon Gateway to RFC-822 (RFC-822.MBF v3)

$BODY$

2)  SMF70.MBF

# smf70.mbf - mailbox format for SMF minimal submission format

# version 1.1

; msg-prefix = SMF

; msg-ext =

SMF70

TO: $RECIPIENTMAILBOX$ @ $RECIPIENTDOMAIN$

FROM: $SENDER$

SUBJECT: $SUBJECT$

DATE: $DATESTAMP$

ATTACHMENT: $ATTACHMENTS$

O-SMTP-HEADER: $HEADERS$

$BODY$

3)  DIGEST.MBF

# digest.mbf - default message format for digest mail

# version 1.0

Date: $HEADER:DATE$

From: $HEADER:FROM$

Subject: $HEADER:SUBJECT$

$BODY$


Mailing Lists

Mailing Lists, sometimes called Email Groups or Distribution Lists, allow groups of users to be addressed as if they all shared a common mailbox. Copies of email messages sent to the list are distributed to each of the list’s members. Lists may contain members with local and/or remote destination addresses, be public or private, moderated or open, be sent in Digest or normal message format, and more.

Mailing List Editor

The Mailing List Editor is used to create and maintain Mailing Lists and can be reached from the Lists|New List… or Lists|Edit List… menu selection. Its eight sections are:

Options

Members

Routing

Subscriptions

Support Files

Notifications

Security

Digest

Creating a New Mailing List

When the Lists|New List… menu selection is chosen, the Mailing List Editor will be opened for creating the new list. Naming the list and designating the domain to which it will belong are the only required parameters for creating it. All other options will contain default settings. You can change these settings while creating the list or you can change them later by editing it.

Modifying an Existing Mailing List

Click the Lists|Edit List… menu selection to open the Select Mailing List dialog. This dialog is identical to the Select Account dialog and is used to choose the Mailing List that you wish to edit. When a list is selected from this dialog it will be opened in the Mailing List Editor for editing or review.


 Options

List Addresses

Name

Specify a name for the mailing list and then choose the domain to which the list will belong form the drop-down list box. Messages directed to this list will use the name and domain specified here (e.g. mylist@mydomain.com). List names cannot contain "!" or "|".

List’s "reply-to:" address

Type the email address to which you want replies to this list to be directed.  Enter the list’s address if you want replies to be directed back to the it. You may enter an address other than the list name, or choose an address from the drop-down list if you want replies to this list to be directed to an alternate address. If you leave this field blank then replies to any list message will be directed back to the sender of that message.

List Properties

This list is private and only members can send list traffic

When this control is enabled, the list will only propagate messages from list members.  Messages originating from non-members will be deleted.

This list responds to EXPN and LIST requests

If this option is selected the membership of the list will be reported in response to an EXPN or LISTS command during a mail session.  Otherwise, the list’s membership will be kept private.

Messages have list name in subject

This setting causes MDaemon to enclose the name of the list in brackets (e.g. [ListName]) and add it to the beginning of the Subject: in all messages sent to the list.

Messages have thread numbers in subject (ie…subject text {5} )

This switch allows you to toggle whether thread numbers will be displayed in the Subject: header of list messages. They are appended to the end of the subject line in braces and used as a pseudo-thread number. Sorting your inbox by subject will align list mail in chronological order.

Delivery precedence level for this list’s traffic

Enter a number from 0-99 in this control. This value signifies the relative sort order of the messages during the delivery process. The lower the value, the higher its importance and the further up it will be in the sort order within a message queue.

Replace ‘TO:’ field with: N/A, list’s name, member’s full name

Use these options to designate what address will be displayed in the TO: field whenever MDaemon receives a message directed to the list.

N/A - When N/A is selected MDaemon will make no changes to the address displayed.  The address contained in the TO: field will appear exactly as the sender of the message entered it.

Member’s Name - When this option is selected, the TO: field will contain the address of the list member to whom the message is directed.

List’s Name - This option displays the address of the Mailing List in the TO: field.

Note
The Member’s Name option can only be chosen when "MDaemon Will Crack List Mail" has been selected on the Routing tab of the Mailing List Editor.  When "Route A Single Copy…" is selected, MDaemon will default to the List’s Name option.

Include "[listname] list member" in TO: field

When this feature is enabled, "[Listname] List Member" will be displayed in the "real name" portion of the message’s TO: field.

Note
Not all email clients support the displaying of "real names" in the TO: field of messages. In such clients only the actual email address designated in the "Replace TO: Field With…" feature will appear.

Don’t distribute messages larger than xx bytes

This control places an upper limit on the size of a message accepted for this mailing list.  Messages larger than this limit are sent to the bad message directory.


 Members

Membership

Current member count:

This control displays the current number of users subscribed to the list and lists them in the box below. Each member’s entry also states his or her "type" of membership: normal, digest, read only, or post only.

Remove

This button removes the selected entries from the Current Members list.

Digest

Select a member and then click this button to make it a "Digest " membership.

Read only

Click this button after selecting a list member to give their membership "Read Only" status. They will still receive messages from the list but will not be allowed to send them to it.

Post only/no mail

Clicking this button after selecting a member will set their membership to "Post Only". They will be allowed to send messages to the list but will not receive any.

New member email

Enter the email address of the person you wish to add to the mailing list. Member’s addresses cannot contain "!" or "|".

New member real name

Enter the member’s name in this field. This name will appear in the "To:" field of their list messages when the "Replace ‘TO:’ field with: member’s full name" option is selected on the Options tab.

Normal, digest, read only, post only

Click the option that you want to be applied to the New Member’s Email Address.

Add

This button adds the entry in the New Member’s Email Address control to the Current Members list.

Default

Click any one of the options next to this button (Normal, Digest, Read Only, Post Only) and then click the button to make that option the default setting for new members.

Automatically remove dead addresses from list membership

When this feature is enabled, MDaemon will automatically remove an address from the Members list when it encounters a permanent fatal error while attempting delivery.  Addresses will also be considered "dead" and removed when their message is moved to the Retry system and subsequently expires from that system.


 Routing

MDaemon will crack list mail

If selected, individual list messages will be created and dispatched to each list member.  This will result in numerous individual messages being created which could effect the server’s performance.  This option is appropriate for a mailing list of around 15 members or less.

Generate unique message id for each copy

When MDaemon cracks list mail it creates an individual copy of the message for each member.  If you wish MDaemon can make certain that each copy of the list message contains a unique identifier.

Route single copy of list mail to this smart host | host name

If selected, MDaemon will route a single copy of each list message to the specified smart host.  This method employs multiple RCPT TO commands during the SMTP session with the specified host.

Ignore errors when spooling list mail to host

Since some smart hosts will refuse to queue or spool mail for certain domains, the routed approach to list delivery could cause numerous problems.  An error code returned from the smart host as a result of this refusal would ordinarily cause MDaemon to abort the delivery attempt.  If this switch is set MDaemon will ignore error codes returned from the smart host during delivery of routed list mail thus allowing those members that are accepted a chance to receive the list message.

This host allows [XX] RCPT TO’s per message (0=no limit)

Some hosts limit the number of RCPT TO statements that they will accept when you are attempting to route a single copy of a message through them. If you specify the limit in this control then MDaemon will work around it by creating additional copies of the message and dividing the list into smaller groups. Then it will deliver the message to those groups thus avoiding the need to exceed the limitation. This is similar to "cracking" the list, but into groups instead of individuals.


 Support Files

New Member Welcome File

If specified, the file listed here will be processed and mailed to all new members just after they subscribe. The file is processed and handled exactly the same way as Auto-Response scripts and may therefore contain any macro available to them.

See:

Creating Auto Response Scripts

Apply This Suppression File

If specified, the file listed here will be used to suppress messages sent from specified users.

Apply This Header/Footer File

The contents of the files specified here will be used as the header and/or footer file for list messages.


 Notifications

Notification Options

Send a message to

This control lists an address that will be notified when the selected events take place.

When a user subscribes to this mailing list

If selected, a note will be sent to the address specified in the associated control each time someone subscribes to the mailing list.

When a user unsubscribes to this mailing list

If selected, a note will be sent to the address specified in the associated control each time someone unsubscribes to the mailing list.

When a message arrives which exceeds the max size limit

If selected, a note will be sent to the address specified in the associated control each time someone sends a message to the mailing list that is larger than the maximum acceptable size.  Such messages are moved into the bad message directory.

Notification Options

Notify non-members of message rejection (private lists only)

When non-members of a private list send mail to the list, MDaemon will inform them that the list is private.  They will also be given instructions on how to subscribe to lists.

Notify subscribers/unsubscribers on the status of their requests

When this checkbox is enabled MDaemon will send a completion notification message to the user that has been subscribed/unsubscribed to the Mailing List.

Returned Mail

Send all mail returned to the list to

Here you specify who should receive any returned mail generated from list traffic. For example, a mailing list with 100 recipients will generally have 10-20 undeliverable addresses either due to address changes or down servers or whatever. The SMTP system will generate and return to the sender of the message notification mail concerning these undeliverable conditions. You can configure who should receive these messages for your mailing lists. You can also specify that no one should receive them in which case MDaemon will place list mail into the mail stream in such a way that return mail will not be possible.


 Security

List Administration

Password

Enter the lists access password in this control.

List Moderation

This list  is moderated by

If set, the list will be moderated by the specified user.  Moderated lists forward all posts to the moderator.  The moderator alone may submit or forward messages to the list.

Anyone can post who knows the list’s password

If this option is checked the moderator can assign a password to the mailing list.  Messages submitted to a moderated list that have the appropriate password specified as the first X characters of the subject line will not be subject to moderation - that is, the message will be immediately posted as if it had come from the moderator.

For example:  to bypass the moderator on a moderated list called MDSUPP, which has a password of ALTN, make ALTN the first 4 characters of the message subject.

Membership Limit

Limit this list’s membership to [xx] members (0=no limit)

With this feature you can place an upper limit on the number of people who are allowed to subscribe to the Mailing List.  Enter a zero into this field if you do not wish to limit list subscriptions.

Note
This limit is only placed upon those who can Subscribe to the list through the Subscribe command.  This limit does not apply to subscriptions entered through the MDaemon interface, or through Subscription commands that are accompanied by the list Password.


Subscriptions

Subscribe

Allow people to subscribe to this mailing list via email

This switch controls whether or not the list will allow potential members to subscribe to the mailing list by sending a subscription request to MDaemon.

Authenticate subscription requests

With this switch set MDaemon will attempt to authenticate the subscription request.  The mechanism employed to accomplish this consists of MDaemon generating a unique password string for the subscription transaction.  A message is sent to the potential member which contains this unique password.  Once the potential member responds by replying to this message MDaemon will then add the member to the mailing list’s membership.

Authenticate auto-responder generated subscribers

Click this option if you want authentication to be required when the member is added via the Add Sender to This Mailing List Auto responder feature.

Unsubscribe

Allow people to unsubscribe from this mailing list via email

This switch controls whether or not the list will allow members to quit the mailing list by sending an unsubscription request to MDaemon.

See:

Remote Server Control Via Email

Authenticate unsubscription requests

With this switch set MDaemon will attempt to authenticate the unsubscription request.  See Authenticate Subscription Requests above for a discussion of the mechanism employed to accomplish this.

Authenticate auto-responder generated unsubscribers

Click this option if you want authentication to be required when the member is removed via the Remove Sender From This List Auto responder feature.

Time to Live (global for all mailing lists)

Outstanding authentication requests expire after xx minutes

When someone is subscribed or unsubscribed, this is the amount of time that they have to confirm the subscription command before it will be discarded. MDaemon will generate a confirmation message and send it the subscribed address. The recipient must reply to the message within the designated time limit before the subscription command will be considered valid. This value is global; it applies to all MDaemon mailing lists not just the one that is currently being edited.

See:

Subscribing to Mailing Lists


Subscribing To Mailing Lists

To subscribe to a mailing list, a person sends an email message addressed to MDaemon (or any alias thereof) at the domain hosting the mailing list, and places the subscribe command as the first line of the message body.  For example, if a mailing list called MDSUPP is being hosted by a domain called ALTN.COM, one would subscribe by composing a message addressed to "mdaemon@altn.com" and placing the value: SUBSCRIBE MDSUPP as the first line of the message body. The message subject is irrelevant and can be left blank.

For complete details on how to form this and other control messages, see:

Remote Server Control Via Email

Note
Occasionally, users will attempt to subscribe/unsubscribe to lists via email by sending the commands to the list itself rather than to the MDaemon system account. This results in the command being posted to the list rather than the user being subscribed or unsubscribed. To prevent these sorts of messages from being posted to mailing lists you may set the following key in the MDaemon.ini file.

[Special]
PreProcessListMail=Yes

This will cause messages containing subscribe, unsubscribe, and signoff commands in the first line of the message body to be rejected when those commands contain the list name and are sent to the list’s address rather than the system account.

You can also utilize MDaemon’s Auto Responder features to automatically subscribe members to a list.


 Digest

Digest Settings

Enable digest support for this mailing list

This control determines whether this mailing list support message digests. When digest support is enabled a copy of each message sent to the mailing list will be archived. Members of the mailing list who have elected to receive traffic from this list in digest form will be sent these archived messages in a compact and easy to use indexed format.

Insert HTML shortcut links into digest messages

When this control is enabled, MDaemon will convert all URLs found within digest messages to hypertext links.

Force all members to use digest mode

By default, list members can control whether they wish to receive list traffic in digest or regular format. This control forces all members to use digest mode irrespective of the mode they may have chosen for themselves.

Storage format

Select the MBF file that individual messages placed into the digest will be conformed to. The default DIGEST.MBF file provides typical functionality comparable to most other mailing list software. For complete details on how to create MBF files see Creating and Using MBF Files.

Edit MBF

Click this button to edit the Mailbox Format file listed in the Storage format control.

When to Spool Digest Messages

Send digest mail at 9, 12, 3, 6 AM and/or PM

Mailing list digests must periodically be sent to those list members who are set to receive mail in digest format. These controls allow you to configure when you wish MDaemon to do this.

Spool digest mail if [xx] messages have accumulated (0 = n/a)

Sometimes digests should be sent to list members based upon the number of messages that have accumulated rather than (or in addition to) specific times. This control allows you to specify the number of messages that the list will accumulate before sending the digests to digest mode list members.

Spool digest mail if [xx] lines of message text received(0 = n/a)

This control will cause Digest mail to be sent immediately when a digest grows to this many lines of text.

Permanent Archive

Archive digests into a file catalog / which catalog do you want to use?

These controls allow you to place digest messages into a file catalog so that back-issues of the digests can be collected in the future. MDaemon will generate a unique archive name for each digest and place it into the catalog you specify.

For complete information on how to work with catalogs see:

Catalog Editor


Catalog Editor

Use the Catalogs|New Catalog… or Catalogs|Edit Catalog… menu selection to open the Catalogs Editor for creating or editing a file catalog. Catalogs give users the ability to request files across the network and have them encoded and mailed back to them. Catalogs work by allowing the mail administrator to assign "magic names" (shortcuts) to files on disk. Magic names are like aliases which point to a specific file located somewhere accessible to MDaemon. A user can then use a special type of email message to request the file using the magic name. The format of this special email message is described in the Remote Server Control section (see the GET command in Mailing List and Catalog Control.

Catalog Properties

Name

Use this field to enter a name for the file catalog.

Password

Use this field to enter a password for the file catalog.

Note
With MDaemon v3, a password is no longer required for all catalogs. You may choose to make catalogs accessible without a password.

See:

Mailing List and Catalog Control

Add New File

Add File

Click this button to add a file to the catalog. After choosing the file that you wish to add you will be prompted for the "Magic name" that you wish to assign.

File listing

This window displays all the files and their associated "magic names" currently registered as members of the specified catalog. Double click on an entry in this window to remove it from the catalog.

Remove

Click this button to remove a selected entry from the File Listing.

See:

The Public Catalog


The PUBLIC Catalog

The PUBLIC catalog is an exception to the normal rules governing access to file catalogs.  Typically, to access a catalog requires a password that has been assigned to the catalog.  With the PUBLIC catalog the password is not required.  Files listed in the PUBLIC catalog are available to anyone who knows the file’s magic name.


Domain Gateways

The Gateway Editor is reached by clicking the Gateways|New Gateway… or Gateways|Edit Gateway… menu selection on the Message Router. This feature provides a limited yet useful secondary level of support for hosting multiple domains. When a message arrives for a domain for which MDaemon is acting as a gateway, it is separated from the main mail stream and delivered to the directory specified for it in the Gateway Editor. Additionally, attachments can be automatically extracted and placed in the specified attachment directory. Further, all mail is re-formatted according to its specified MBF file. You can host as many domains as you like using this method.

An example will prove useful here:

Suppose you want to "partially" host a domain for another department. You want to collect its mail and deposit it in a directory but do not want to maintain its accounts on your server. Let’s use "company.com" as its name. The first thing you will do is enter "company.com" in the Domain Name field on the Domain Settings tab of the Editor. Then, you will select and enter the disk directory where incoming mail messages and file attachments should be stored. You don’t have to use the auto-extraction of attachments feature unless it is needed. Finally, either select an existing MBF file or install a new one. The default RFC-822 MBF file will ensure that all mail stored for "company.com" will be in RFC-822 format. Once all the settings have been entered click Apply or Ok.

Now that the domain "company.com" has been installed as a client domain, MDaemon will store all messages that it receives for that domain in the directory specified, and in the format you have dictated—regardless of to whom the messages are directed. In other words, all mail for that domain will be pooled into a single directory on disk. You will setup this directory and a POP account for the domain to access directly from the Gateway Editor by entering a name and password on the Gateway Editor’s POP Access tab and then clicking the Create/Update Account button. All that remains is for the domain to collect its mail from MDaemon via its POP account. This can be done by either a mail client or another MDaemon, which could utilize its DomainPOP feature to further distribute the mail to the domain’s users (as would be the case in our example). Alternatively, you can use the controls on the ESMTP ETRN and ATRN/AUTH tabs so that the domain could collect and distribute its mail to its users via ESMTP instead of POP or DomainPOP.

This all works perfectly for LAN and WAN based systems that can easily be configured to resolve an arbitrarily assigned domain name like the "company.com" example. However, how can Internet email support be provided for "company.com" if the domain doesn’t really exist on the Internet? There are two ways to cope with this problem. First, the domain can be registered with the Internet authorities and configured to resolve to the same IP address as the MDaemon that you want to collect its mail. Better yet, it can be registered as an alias to the primary domain name. Failing this, a message can still be delivered by "hiding" "company.com" within a primary domain address. Using this method addresses can be constructed that will pass through the primary domain and on to the users of the domain for which MDaemon is acting as a gateway. For example, if an outside Internet mail user wishes to send a message to "bob@company.com", which is domain gateway served by "mydomain.com", then the sender would need to address his email message to "bob{company.com}@mydomain.com". Because "mydomain.com" is a registered domain hosted by MDaemon, this message will be delivered properly. When MDaemon receives a message with an address in this format it will convert the address to "bob@company.com" and deliver the message to the disk directory specified for that domain.

See:

Gateway Editor

Primary Domain Configuration

Secondary Domains


Gateway Editor

The Gateway Editor includes the following tabbed dialogs:

Domain Settings*Gateway_Domain_Settings>Main

This dialog contains the domain name of the particular domain that you are working with, as well as the path to the directory used for storing messages and file attachments addressed to this domain. Here you will also assign an MBF file to be used when MDaemon delivers mail to this domain’s mailbox.

ESMTP ETRN*Gateway_ETRN_Dequeue>Main

Use the controls on this dialog to choose whether MDaemon will respond to ESMTP ETRN requests made on behalf of the domain in order to dequeue its messages. To aid in security, this dialog also contains controls that make it possible to assign specific IP addresses that MDaemon will honor these requests from, or you can designate IP addresses that will be ignored.

ATRN/AUTH

Use the controls on this tab if you want MDaemon to respond to ATRN commands from the domain for which MDaemon is acting as an email gateway. The tab also contains controls for specifying the domain’s shared secret necessary for authentication and for designating whether or not authenticated requests should be considered valid regardless of IP address.

Mail Forwarding*Gateway_Mail_Forwarding>Main

With this dialog you can declare a host to which the domain’s mail will be forwarded as soon as it arrives. There is also a control for stating whether a copy of these messages will be kept locally.

POP Access*Gateway_POP_Access>Main

Here you can create a POP account that will have access to this domain’s stored mail. Using the name and password that are assigned here, an ordinary mail client or another MDaemon installation can access the domain’s mailbox and collect its mail.

Quotas

This dialog is used for assigning a limit to the amount of disk space that the domain may use and the maximum number of messages that may be stored.

See:

Gateway Domains


 Domain Settings

Domain Name

Enter the name of the domain for which you wish MDaemon to act as an email gateway.

Mail Directory

Place message files for all users of this domain here

Enter the directory where you want to store incoming mail for the domain.

Automatically extract embedded attachments

Some mail systems require attached files be extracted before submission of mail messages to the mail stream. To facilitate this, MDaemon can auto-extract incoming MIME attachments and place them in the \Files\ subdirectory underneath the domain’s message directory. This directory will only be used if the "Auto-Extract" switch is selected.

Apply This MBF File to Incoming Messages

The MBF file specified here will be applied to all incoming messages that arrive for the domain. This allows for any special reformatting that may be required.


 ESMTP ETRN

ESMTP ETRN

Respond to ESMTP ETRN requests made for this domain

When this switch is enabled MDaemon will respond to ESMTP ETRN requests made by qualified hosts on behalf of the domain for which MDaemon is acting as an email gateway. The ETRN command is an SMTP extension that signals a server storing mail for a particular domain that it is time to begin spooling the mail. When MDaemon receives an ETRN request for a domain, it will immediately begin spooling the stored mail for delivery using subsequent SMTP transactions. Please note that the SMTP session that issues an ETRN request will not be the one that receives any stored mail. MDaemon will use subsequent independent SMTP transactions to send any mail it has stored for the domain. This preserves the message envelope and is more secure. Also note that the host to which MDaemon will spool any stored mail may not immediately begin reception of these messages. ETRN only guarantees that any stored mail is spooled for delivery. The actual process of delivery is subject to other administrator-imposed restrictions and may have to wait in the outbound mail queue for the next scheduled remote mail processing event to take place. Because of these limitations we recommend using On-Demand Mail Relay (ODMR) and its ATRN command rather than ETRN. This method is not supported by all clients and servers, however, and will therefore only be available to client domains using a server that does so. MDaemon fully supports ODMR on both the client and server side.

Spool all mail to this host

This is the host name or IP address to which any stored mail will be sent when an ETRN request is received and honored.  This machine must be running an SMTP server to receive these messages.

If the domain listed above is local treat it as if it were foreign

Activate this control if the domain is local but you want its mail to be spooled as if it is remote.

Spool all mail to IP of machine making ETRN request

Selecting this option will cause MDaemon to send any stored mail to the IP address of the machine that made the ETRN request. The requesting machine must be running an SMTP server to receive these messages.

Use this port when spooling mail

Use this control to specify the port on which the domain’s mail will be spooled.

IP Access

Honor ETRN requests from these IP’s

Select this switch and MDaemon will honor ETRN requests made from any IP listed in the associated address list.

Ignore ETRN requests from these IP’s

Select this switch and MDaemon will ignore ETRN requests that are made from any IP listed in the associated address list.

Add new IP

To add a New IP to the current list simply enter the IP into this text box and click the ADD button.

Remove

Click this button to remove a selected entry from the list of IP addresses.

TIP
Although there is nowhere on this screen to enter it, you can control the SMTP envelope ID that MDaemon will use when spooling the domain’s mail. The following key controls this in the GATEWAYS.DAT file:

[GatewayDomainName]
EtrnAs=address@domain.com


ATRN/AUTH

ESMTP ATRN

Respond to ESMTP ATRN commands for this domain (requires AUTH)

Activate this control if you want MDaemon to respond to ATRN commands from the domain for which MDaemon is acting as a gateway. ATRN is a new ESMTP command used in On-Demand Mail Relay (ODMR), which is currently the best relay method available for mail hosting. It is superior to ETRN and other methods in that in requires authentication before mail is dequeued and does not require a static IP address. A static IP address isn’t required because the flow of data between MDaemon and the client domain is immediately reversed and the messages are despooled without having to make a new connection—unlike ETRN, which uses a separate connection after the ETRN command is sent. This enables client domains using a dynamic (non-static) dialup account to collect their messages without having to use POP or DomainPOP to distribute them to their users because the original SMTP envelope is preserved.

ESMTP AUTH

Dequeuing mail requires authentication

When you have configured the settings for this domain to accept ESMTP ETRN requests, you may use this tab’s controls to require the connecting host to first authenticate itself using the ESMTP AUTH command. Since ATRN requires authentication, this control must be enabled before MDaemon will respond to ATRN requests.

AUTH shared secret

Enter the client domain’s "Shared Secret" or password here that will be used during authentication.

Note:
The domain for which MDaemon is acting as a gateway must use its domain name as the logon parameter.

Authenticated requests are valid regardless of connecting IP

Enable this checkbox if you want to honor authenticated requests regardless of the IP address from which they are coming. If this control is not enabled then only requests from those IP addresses specified in the IP Access section of the ESMTP ETRN tab will be honored.


 Mail Forwarding

Forwarding Properties

Forward mail to this host

Sometimes it is advantageous to simply forward a copy of all messages for a domain as they arrive.  If you wish to configure MDaemon to do this then enter the name or IP address of the SMTP server to which copies of incoming mail for this domain should be sent.

Forward mail to this address

Use this feature if you wish to forward to a specific email address all email messages destined for this client domain.

Use this address in SMTP envelope

MDaemon will use this address in the SMTP "Mail From" transaction.

Forward mail using this TCP port

MDaemon will forward this mail using this TCP port.

Retain a local copy of all forwarded messages

Select this option if you wish MDaemon to retain a copy of a message locally once it has been forwarded.


 POP Access

Early versions of MDaemon pioneered a method of mail collection known as DomainPOP.  You can configure domains for which MDaemon is acting as an email gateway so that MDaemon will be their DomainPOP host. In other words, all the mail for the domain will be collected in a single mailbox on your server. With the controls on this tab you can create an account in your user list that will have access to these messages. This account can also be accessed using a regular POP client instead of an MDaemon, though in that case DomainPOP parsing would not be available.

Name

Enter the POP USER name that the client domain will use to access the messages stored in its mailbox.

Pass

Enter the POP PASS password that the client’s domain will use to access the messages stored in its mailbox.

Create/update account

Click here to create an account or to update the NAME and PASS values if the account already exists.

Note
You can completely edit (or even remove) an account using the Account Editor. Be careful if you remove an account because that will delete the account’s mail and file directories - which also happen to be the ones the gateway is using!


Quotas

Quota Options

This gateway must observe these quota settings

Here you can specify the domain’s maximum number of allowable messages and the maximum amount of disk space (in kilobytes) that it can consume. This includes any decoded file attachments in its Files directory.

Place a warning message in gateway mail directory when over quota

If this control is enabled and a mail delivery to the domain is attempted that would exceed the maximum message or disk space limitations, the message will be forwarded to the designated address along with an appropriate warning.

Address warning message to

Specify the address to whom the over quota warning message should be sent.

Address warning message from

Specify the address from whom the over quota warning message should appear to have been sent.


Queue and Statistics Manager

MDStats Queue and Statistics Manager Version 3.

MDStats v3 is accessed directly from within MDaemon by choosing the Queues|Queue and Statistics Manager… menu selection.  MDaemon Queue/Stats Manager is made up of a four-page dialog.  Each of these pages has been designed to serve a distinct and specific purpose while also maintaining a simple format that makes them very easy to use.

Queue Page

The default tab is the Queue Page.  From this page you can easily manage all of MDaemon’s standard mail queues, as well as the User Account mailbox folders.  By simply clicking on the queue or user of your choice, a list of all message files contained within the specified queue will be displayed along with several key pieces of pertinent information about each message: the sender, the recipient, the content of the "Deliver-To" header, the subject of the message, its size, and how long it has been at its current location.  In addition, controls are provided that make it easy to copy or move messages between folders, or delete them completely.

User Page

The User Page displays a list of all MDaemon users. This list includes their full name, mailbox name, the number of messages in their mailbox, the amount of disk space that their account is taking up, and the date that they last checked their mail.  This list can also be saved to disk as a text file, or it can be saved in comma delimited format for use with databases.

Log Page

With this dialog you can display MDaemon’s Log Files in a simple list format.  This feature is very useful for quickly examining the history of MDaemon’s mail transactions because it condenses the selected Log File into a columnar list which contains: the Type of the message (POP Inbound, DomainPOP, RFC822, and so on), the Host to which MDaemon connected during the transaction, the sender, the recipient, the message size, the date that each message was processed, and whether or not the transaction was successful. You can also examine the detailed portion of the log regarding any of the entries on the list by double clicking the desired entry.  This will display the portion of the log where that transaction was made.  Logs displayed on the Log Page can be saved as a text file or in comma delimited format for use with databases.

Report Page

The last tab is the Report Page.  With this feature you can produce a report containing all of MDaemon’s configuration settings, written in a plain text readable format.  Because of the large number of optional settings and configurations in MDaemon, this can greatly speed the process of administering configuration changes as well as aid in diagnosing possible configuration problems.  Additionally, this report is displayed in a text editable format that makes it possible to Copy/Paste the information it contains (using the right-click shortcut menu), or add notations or other information to the file before saving it.


Queue Page

Queue page list box

When a queue or user is chosen from the Message Queues area or the user list box beside it, a list of all message files contained within the selected queue will be displayed in the main list box on this page.  This list contains each message’s file name, the sender, the recipient, the content of the "Deliver-To" header, the subject of the message, its size, and how long it has been at its current location (listed by date and time).

Above this box the complete file path to the currently displayed directory is given, as well as the number of messages displayed and the size of the directory.

You may copy, move, or delete one or more files by selecting them from the list and then clicking the appropriate button below it.

The content of these files may also be edited directly from the Queue Page list box.  Simply double-click the file that you wish to edit (or choose "Edit" from the right-click shortcut menu) and MDStats will open the file for editing in Window’s Notepad.

Note
If you want MDStats to open an editor other than Notepad by default, then you must edit the "mdstats.ini" file located in the \mdaemon\app\ directory.  Change the "Editor=" key located under the [QueueOptions] section heading to "editor=youreditor.exe" (without the quotes).  If the file path of the *.exe file is not in your current path, then you will have to include the path here as part of the file name.

The list box can be navigated by using the vertical or horizontal scroll bars, or you can click anywhere within the list box and use the ARROW keys for navigation.  You can sort information contained in the Queue Page list box by whichever column you choose.  Simply click once on the desired column to sort it in ascending order (A-Z, 1-2), or click twice to sort it in descending order (Z-A, 2-1).  Columns can also be resized by positioning the pointer over the line between any of the column headings until it changes shape and then dragging the column to the desired width.

Selecting Files

To select files individually	Click the desired file.

To select contiguous files	Click the first file in the contiguous list of files that you wish to select, then while holding down the SHIFT key, click the last contiguous file in the desired list.

Alternatively, you may use the ARROW, HOME, END, PAGE UP, and PAGE DOWN keys, while holding down the SHIFT key, to select files in contiguous order.

To select non-contiguous files	Click on the desired files in the File Name column while holding down the CTRL key.

Message queues

Click an option button in this area and a list of all files contained within the specified queue will be displayed in the Queue Page list box.  If you click the User Folders option, a list of all MDaemon users will be displayed in the User List Box to the right of the Message Queues section.

Users list box

This box displays a list of all MDaemon users when the User Folders option is clicked in the Message Queues section.  Click a user’s name to display a list of all message files currently contained in the user’s mailbox folder.

Refresh

Because mail queues are dynamic while MDaemon is active - with message files constantly being transferred to and from them - you should regularly click this button to refresh any list of files that you may have displayed.

Note
You can edit the MDstats.ini file to cause displayed lists to automatically refresh.  To do this simply open the MDstats.ini file located in MDaemon’s \app\ directory and edit the AutoRefresh key under the [QueueOptions] heading to reflect the number of seconds that you wish to elapse between refreshes.  Entering the value 0 means that you do not want the list to automatically refresh.  Example: AutoRefresh=15 (the list would refresh every 15 seconds).

Copy

When one or more files are selected, click this button to copy the selected files to another queue or user’s mailbox folder.  After clicking this button the Copy Message(s) dialog box will open, from which you can select the desired location to which you wish to copy the selected files.

Move

When one or more files are selected, click this button to move the selected files to another queue or user’s mailbox folder.  After clicking this button the Move Message(s) dialog box will open, from which you can select the desired location to which you wish to move the selected files.

Note
Files copied or moved to other queues will rarely retain their original file names. To avoid overwriting files of the same name that may already be in the queue, MDaemon always calculates the next destination filename based on the HIWATER.MRK file located in the destination folder.

Delete

When one or more files are selected in the Queue Status List Box, click this button to delete the selected files.  After clicking this button a confirmation box will open asking if you really do wish to delete the selected files.

Note
Mail queues are dynamic while MDaemon is active - with message files constantly being transferred to and from them.  For this reason you should be aware that when copying, moving, or deleting files you may at times encounter a message from MDStats stating that it cannot complete the action that you are attempting.  This will occur when the message file that you are attempting to work with has already been removed by MDaemon before the desired action has begun.  By clicking the Refresh button, you can update the current list of files displayed in the list box.

 You can prevent messages from being moved out of the queue while you are editing them by editing the MDstats.ini file. To do this simply open the MDstats.ini file located in MDaemon’s \app\ directory and change the LockOnEdit=No key under the [QueueOptions] heading to LockOnEdit=Yes.  This will cause a LCK file to be created whenever you are editing a message, which will prevent it from being moved out of the queue until you are finished with it.


User Page

User information

When the User Page is chosen MDStats immediately loads a list of all MDaemon accounts into the User Information list box.  This list contains each user’s full name, the name of their mailbox, the domain to which the account belongs, the number of messages it contains, its mail format, the amount of disk space (in bytes) that the account is taking up, their forwarding address, and finally, the date that their mail was last checked. Given that the information contained in this list is constantly changing, it can be easily updated by clicking the Refresh button.

The list box can be navigated by using the vertical and horizontal scroll bars, or you can click anywhere within the list box and use the ARROW keys for navigation.  You can sort information contained in the User Information list box by whichever column you choose.  Simply click once on the desired column to sort it in ascending order (A-Z), or click twice to sort it in descending order (Z-A).  Columns may also be resized by positioning the pointer over the line between any of the column headings until it changes shape and then dragging the column to the desired width.  Further, you can double-click any entry and MDStats will be shifted to the Queue Page with the contents of their mailbox folder displayed.

Note
By default, the list displays the Message Count not file count, and the Disk Space used by messages not the space used by all files in the directory.  This is the Quota information reported by MDaemon.  Alternatively, MDStats can display the file count and disk space used by all files instead of by messages.  To change this setting simply open the MDstats.ini file located in MDaemon’s \app\ directory and change the ShowQuota=Yes key under the [UserOptions] heading to ShowQuota=No.

• Warning!
User folders contain a file called "hiwater.mrk" that MDStats reads to determine some of this user information.  You should avoid deleting this file unnecessarily as it will prevent MDStats from being able to obtain some of the information listed in the User Information list box.

Refresh

User statistics such as the number of messages contained in their mailboxes, and the amount of disk space that their accounts are using, are constantly changing.  You can easily update the information contained in the User Information list box by clicking the Refresh button.  This will immediately make all displayed information current.

Progress indicator

Because User Information lists can at times be very large, below the User Information list box is a progress indicator bar that provides a visible indication that the program is still operating when large files are being loaded by MDStats.

Save

The information contained in the User Information list box can be saved as a file in comma delimited format for use with databases, or as a plain ASCII text file by clicking the Save button.  After choosing a name and location for this file in the Windows Save As dialog, MDStats will ask you whether you want to save the file in comma delimited format or as a plain text file.


Log Page

Log report

The Log Report list box displays MDaemon’s detailed log files that you select through the Open Log button and the Windows Open dialog that follows it.  The Log Report display provides a quick and easy way to review the history of mail transactions that MDaemon has processed without having to sort through the large volume of information that MDaemon log files may sometimes contain.  When a Log Report is displayed in this list box MDStats breaks it down into a simple format containing: the Type of the message (POP Inbound, DomainPOP, RFC822, and so on), the Host to which MDaemon connected during the transaction, the sender, the recipient, the message size, the date that each message was processed, and whether or not the transaction was successful.

You can also examine the detailed portion of the log regarding any of the entries on the list by double clicking the desired entry.  This will display the portion of the log where that transaction was made.  Using the right-click shortcut menu you can copy/paste this detailed log portion to a text editor for saving or editing should you desire to do so.

The list box can be navigated by using the vertical and horizontal scroll bars, or you can click anywhere within the list box and use the ARROW keys for navigation.  You can resize the list box’s columns by positioning the pointer over the line between any of the column headings until it changes shape and then dragging the column to the desired width.

Note
The Log Page will display log files that have been compiled using either the Log Detailed Mail Sessions or the Log Summarized Mail Sessions option located in MDaemon’s Setup | Log File menu selection.  However, we highly recommend that you use the Log Detailed Mail Sessions option instead of the Summarized option.  When using the Log Summarized Mail Sessions format you will find that there is very little information that will be displayed in your Log Report.  Because the Log Page itself condenses the detailed log into a summary view of MDaemon’s activity, while still providing the ability to look at the detailed view of every transaction when necessary (by double-clicking an entry), there is no need to have MDaemon summarize the log file while compiling it.

Open log

Click this button to open the Windows Open dialog for choosing which log file that you wish to view.  The default folder that this dialog will display is the Log File directory that you have designated in the MDaemon menu selection Setup | Primary Domain | Directories.  If you click this button when there is a Log File already displayed in the Log Report list box, MDStats will give you the option to append the new file to the one that is currently being displayed.

After a log is displayed, a message box will be opened which contains a summary of the selected log.  When saving a Log Report as a text file, this log summary will be appended to the file being saved.

Progress indicator

Because Log Files can be very large, below the Log Report list box is a progress indicator bar that provides a visible indication that the program is still operating when large files are being loaded or saved by MDStats.

Save

The information contained in the Log Report list box can be saved as a file in comma delimited format for use with databases, or as a plain ASCII text file by clicking the Save button. After choosing a name and location for this file in the Windows Save As dialog, MDStats will ask you whether you want to save the file in comma delimited format or as a plain text file.


Report Page

Report

When the Report Page is clicked MDStats will produce a comprehensive report that lists every setting within MDaemon in an easily readable text format.  This feature greatly decreases the amount of time needed by an administrator to check MDaemon’s many configuration settings, and it can aid in quickly solving possible configuration problems.

You can navigate through this report using either the scroll bars or the CURSOR keys, and the Report display is also a text editor - making it possible to insert notations or additional information that you may want on the report before saving it to a file.  Additionally, you can use the shortcut menu to Cut, Copy, and Paste, to and from this display by right-clicking your mouse and making the desired selection from the menu that opens.

Refresh

Click this button to update the currently displayed Report of MDaemon settings.

Progress indicator

As with the other tabs in MDStats, the Report Page contains a progress indicator bar that serves as a visible indicator that the program is still operating while large files are being loaded or saved.

Save

Click this button to save the currently displayed Report.  After clicking this button a standard Save As dialog will open so that you can designate a file name and location where you want to save it.


Customizing the Queue/Statistic Manager

The following is a list of settings that can be modified in the MDstats.ini file located in MDaemon’s \app\ directory:

MDStats.INI File

[MDaemon]
AppDir=C:\mdaemon\app\	Location of MDaemon’s \app\ directory.
[QueueOptions]
Editor=NOTEPAD.EXE	Editor to use when a message is double-clicked, or when a message is right-clicked and then Edit is selected.
LockOnEdit=No	Whether or not to create a LCK file when editing a message.  This will prevent a message from being moved out of the queue while it is being edited.
AutoRefresh=Yes	Time (in seconds) between auto refreshes of the message listing. 0 means no auto refresh.
ShowDirectories=Yes	Show subdirectories of the queues in the list box in addition to the messages. Directories will appear as <DirectoryName>.
[UserOptions]
ShowQuota=Yes	Determines whether the user listing displays quota information (message count and disk space just like MDaemon calculates it) or file information (number of files and total disk space).
[LogOptions]
ShowUnknown=Yes	Show sessions that MDStats couldn’t determine if they were inbound or outbound, SMTP or POP.
ShowSmtpInbound=Yes	Show SMTP inbound sessions.
ShowPopInbound=Yes	Show POP inbound sessions (mail checks).
ShowSmtpOutbound=Yes	Show SMTP outbound sessions.
ShowPopOutbound=Yes	Show POP outbound sessions (MultiPOP, DomainPOP).
ShowRFC822=Yes	Show RFC822 local mail deliveries.
ShowSmtpHelo=Yes	For SMTP inbound sessions, show HELO domain in the Host column.
IgnoreEmptyPop=Yes	Ignore mail checks when no mail was deliverd.
ShowImap=Yes	Shows IMAP Sessions.
[Remap]	Drive letter remapping; for running MDStats from a different machine than the one MDaemon is on.
C:=\\server\c	When reading from MDaemon.ini, replace "C:" with "\\server\c".
[Special]
OnlyOneInstance=No	Allow only one instance of MDStats to run. Attempting to open it again will activate the instance that is already running.
See:

MDStats Command Line Parameters


MDStats Command Line Parameters

Note: All command line parameters are not case sensitive.

Number 1 through 8	Display a specified queue in the Queue Page.
	1 = Remote Queue
	2 = Local Queue
	3 = Retry Queue
	4 = LAN Queue
	5 = RAW Queue
	6 = Bad Queue
	7 = SmtpIn Queue
	8 = Save Queue
/L[N] [InputFile] [OutputFile]	Produce a log file report.  Specifying an ‘N’ after the ‘L’ means do not save as a comma delimited file.
/A	If producing a log file report, append new information to the output file rather than overwriting it.


MDaemon's Text Editor

MDaemon Server v3 provides a Text Editor which may be opened with the FILE | NEW menu selection.  The Text Editor can be useful for quickly creating data files for use with Auto Responders and various other MDaemon features, such as MBF and RAW files.

See:

Editing MDaemon Files


Editing MDaemon Files

MDaemon’s text editor can also be used to edit a number of existing files used by MDaemon. You can open these files by using the menu option: File|Open|[Filename].  If the file that you wish to edit is not listed on the Open menu then click the Generic Document option.  When you have finished editing the file click File|Save or Save As…

Here is a list of all the documents currently listed on the Open menu:

•	Server usage policy statement

•	HELP message

•	New user welcome message

•	Account information message

•	Transient delivery failure message

•	Permanent delivery failure message

•	Delivery return-receipt message

•	"No valid command found" message

•	"No such user here" message

•	MX cache database

•	IP cache database

•	IP shield database

•	No-cache database

•	Relay control database

•	Domain alias database

•	Account alias database

•	MIME type definition database

•	IP screen database

•	Global suppression database

•	Priority mail database

See:

MDaemon's Text Editor


The RAW Message Specification v3.1

MDaemon Server v3 has inherent support for a simple and powerful mail message format known as RAW mail.  This specification was developed in 1994 for a corporation that needed a custom MTA focusing on easy mail client development. The purpose of the RAW system is to provide a simple and standard format which software systems such as MDaemon can use to create the much more complex RFC-822 compliant message. Use of mail transport agents such as RAW allow client software to offload to the server all the complicated work of maintaining adherence to Internet mail standards.

RAW mail consists of a series of required and optional text headers followed by a message body.   Most headers consist of a token followed by a value enclosed in <> symbols.  Each header line ends with a <CRLF> combination of characters.  All text, headers and body, are plain ASCII and are contained in a file which ends with the extension: RAW.  Headers are separated from the message body by a blank line and are case insensitive.  The from and to headers are the only ones which are required.

From <mailbox@host.com>	This field contains the email address of the sender.
To <mailbox@host.com [, mailbox@host.com]>	This field contains the email address(es) of the recipient(s).  Multiple recipients can be specified by separating each one with a comma character.
ReplyTo <mailbox@host.com>	An optional email address where replies to this message will be directed.
CC <maibox@host.com[, mailbox@host.com]>	An optional list of carbon copy recipients of this message.  Multiple carbon recipients can be specified by separating each one with a comma character.
Subject <text>	An optional subject for the message.
Header <Header: Value>	Allows you to explicitly place Header/Value combinations into the message.
See:

Special fields supported by RAW v3.1

Sample RAW mail messages:


Special fields supported by RAW v3.1

File attachment and encoding:

X-FLAG=ATTACH <filepath, method> [-X]

Example: X-FLAG=ATTACH <c:\utils\pkzip.exe, MIME> -x

This X-FLAG specifies the value "ATTACH" along with two parameters within the <> characters.  The first parameter is a complete path to the file which should be attached to the message.  The second parameter which is separated from the first by a comma character and specifies the method of encoding that is to be used when attaching the message.  MDaemon Server v3 supports two values for this parameter.  The method of MIME instructs the server to use the Internet standard Base64 method of message encoding.  The method of ASCII instructs the server to simply import the file into the message.   An optional -X parameter at the end of the string instructs the server to remove the file from disk once it has been attached.

Delivery Status Notification:

X-FLAG=CONFIRM_DELIVERY

When converting a RAW message which contains this flag into RFC-822 mail, the string is transformed to the "Return-Receipt-To: <sender@host.org>" construct.

Placing Specific Header/Value Combinations into the RFC-822 Message:

If you wish to place a specific header/value combination into the RFC-822 message which will be generated from a RAW file, you will need to use the HEADER macro.  For example, if you want the header "Delivered-By: mail-machine@domain.com" to be placed into the RFC-822 message you would place this: "header <Delivered-By: mail-machine@domain.com>" in the RAW message.  Note that the "header" macro requires both the field and value.  You can place as many "header" macros as you need into a RAW message.

See:

Sample RAW mail messages:

The RAW Message Specification v3.1


Sample RAW mail messages:

1)

from <mdaemon@altn.com>

to <JohnSmith@somewhere.com>

Hello John!

2)

from <JohnSmith@nowhere.com>

to <President@Whitehouse.gov>

subject <Secret FBI Files>

X-FLAG=CONFIRM_DELIVERY

X-FLAG=ATTACH <c:\secret\files\dole.zip, MIME> -X

Here are all those files you asked for.


Remote Server Control Via Email

Many functions of MDaemon Server v3 can be accessed remotely using the email transport system itself. For example, users can gain access to various aspects of their accounts and change or reconfigure them by sending email messages to the server. MDaemon maintains an account for its own use in the user base. This account is reached by sending mail to the mailbox "MDaemon@MDaemonsDomain.com". Messages sent to the server are stored in the server’s message directory just like any other user. At queue run time the server will cycle through all the mail it has received and parse each message for special instructions.

Some of these control messages require a valid account on the server, and are password protected. Users can gain access to their accounts using their account password, and the messages to the server must be directed to "MDaemon@mydomain.com". For those commands which require a valid account on the server, the Subject field of the message must contain the user’s email address and password separated with a comma character (e.g. "Bill@mydomain.com, MyPassword"). Commands are placed within the body of the message. There can be only one command per line but multiple commands can be batched in the same message.

See:

Account Access and Control

Mailing List and Catalog Control

General Email Controls


Account Access and Control

The following section lists the current account access and control commands available to account holders. All of these commands require a "POP Name, POP Password" construction in the subject line. Parameters contained in [brackets] are optional. For example: "name [address]" could be entered as "Lois" alone, or with the optional parameter added ("Lois LLane@dailyplanet.com").

COMMAND	PARMS	DESCRIPTION
ACCOUNT INFO	none	The status of the account passed in the subject line is mailed back to the originator. Ex: ACCOUNT INFO
PASSWORD	new password	The password of the account passed in the subject line will be changed to the one specified. Ex: POP PASSWORD kryptonite
MAILFORMAT	MBF file	The mailbox storage format of the account specified in subject line will be changed to the one specified. A listing of the available formats can be obtained via the MAIL FORMATS command (see General Email Controls section below). Ex: MAILBOX RFC-822
AUTODECODE	Y/N	Automatic decoding of incoming MIME attachments for the account specified in the subject line will be turned on or off. Y=on, N=off. Ex: AUTODECODE Y
BEGIN SIGNATURE	none	Begins recording of a new signature file to be appended to messages generated by the account passed in the subject line.  Subsequent lines will be treated as the text of the signature file until the word END is encountered on a line by itself or the end of the control message is reached. NOTE: The signature file feature is only available for RAW format messages. RFC-822 mail that arrives at the server using SMTP or POP will not append the signature file.  In these cases see your mail client’s documentation for information concerning signature files.
BEGIN AUTORESPONDER	none	Begins recording of a new autoresponder file.  Subsequent lines will be treated as the text of the autoresponder until the word END is encountered on a line by itself or the end of the control message is reached. Ex: BEGIN AUTORESPONDER I’m on vacation right now. I’ll get back to you ASAP. END To erase an active autoresponder use the same command but without any response text. Ex: BEGIN AUTORESPONDER END
FORWARD TO	address	The forwarding address for the account passed in the subject line will be changed to [address] and mail forwarding will be activated for the account. Ex: FORWARD TO vacationing@myhost.com
UNFORWARD	none	Mail forwarding will be deactivated for the account specified in the subject line. Ex: UNFORWARD
MULTIPOP	on/off	MultiPOP will be enabled/disabled for the account specified in the subject line. Ex: MULTIPOP ON Ex: MULTIPOP OFF
See:

Remote Server Control Via Email

Mailing List and Catalog Control

General Email Controls


Mailing List and Catalog Control

None of these commands require an account on the server; thus the subject line need not contain any special value when specifying these instructions.  Parameters contained in [brackets] are optional.  For example: "name [address]" could be entered as "Clark" alone, or with the optional parameter added ("Clark CKent@dailyplanet.com").

COMMANDS	PARMS	DESCRIPTIONS
USERS	none	A listing of all user accounts which are not flagged to hide their information will be mailed back to the message originator. Ex: USERS
LIST	none	A listing of all non-concealed named lists (Mailing Lists that are configured to respond to LIST commands) along with the names and addresses of all members will be mailed back to the message originator. Ex: LIST
	[listname]	Retrieves the membership of the list "LISTNAME" if it is configured to respond to the LIST command. Ex: LIST MDSUPP
	[listname (listpass)]	This command retrieves the membership of the list "LISTNAME" even if it is configured to ignore the LIST command; as long as the list password is correct.  Parentheses around the list password ARE required. Ex: LIST MDSUPP (MYPASSWORD)
SUBSCRIBE	listname [address] [{real name}] [(pass)]	The originator is added to the membership of the specified list provided that list exists and allows remote subscriptions. If an optional address is specified after the list name then that address is added to the list’s membership rather than the address found in the FROM: field of the subscription message. A real name can be added for the subscriber by including it in braces (e.g. {Frank Thomas}. If the list’s password follows this command (parentheses around it are required) then the command will be honored even if this list’s subscribe function is switched off. Ex: SUBSCRIBE mdsupp Ex: SUBSCRIBE mdsupp me@mydomain.com {Frank T} Ex: SUBSCRIBE mdsupp you@yourdom.com (PASS)
UNSUBSCRIBE Or SIGNOFF	listname [address] [(pass)]	The originator is removed from the membership of the specified list provided that list exists and contains the originator as a current member. If an optional address is specified after the list’s name then that address is removed from the list’s membership rather than the address found in the FROM: field of the unsubscribe message.  If the list’s password follows this command (parentheses around it are required) then the command will be honored even if this list’s unsubscribe function is switched off. Ex: UNSUBSCRIBE MDSUPP (MDSPASS) Ex: SIGNOFF MDSupportList me@mydomain.com
UPDATE	listname old-address new-address {real name} (password)	Removes "old-address" from the list and replaces it with "new-address". An optional real name and password value may be given. Ex: UPDATE mdsupp@altn.com old@my.com new@my.com {Mr. M} Ex: UPDATE mdsupp@altn.com old@my.com new@my.com (pass)
SUPPRESS	listname address (password)	This command adds 'address' to the lists suppression file.  The list's password must be provided and the list must already have a suppression file associated with it. Ex: SUPPRESS list@mydomain.com Ex: SUPPRESS me@mydomain.com (PASS)
UNSUPPRESS	listname address (password)	This command removes 'address' from the lists suppression file.  The list's password must be provided and the list must already have a suppression file associated with it. Ex: UNSUPPRESS list@mydomain.com Ex: UNSUPPRESS me@mydomain.com (PASS)
DIGEST	listname [address]	The sender is set to receive mail from the list in digest format.  If an optional address is specified after the list name then that address is set to digest mode. Ex: SET DIGEST MDSupportList Ex: SET DIGEST mdsupp joe@mdaemon.com
NORMAL	listname [address]	The sender is set to receive mail from "list" in normal (non-digest) format.  If an optional address is specifed after the list name then that address is set to receive in normal format instead of the sender. Ex: NORMAL MDSupportList@mydomain.com Ex: NORMAL mdsupp@domain.com joe@altn.com
NOMAIL	listname [address]	This command sets 'address' to nomail mode. The account will enter a suspended state and will no longer receive list traffic. If no address is specified then the originator of the message will be used. ex: NOMAIL list@mydomain.com me@mydomain.com
MAIL	listname [address]	This command returns 'address' to normal mode from nomail mode.  If no address is specified then the originator of the message will be used. Ex: MAIL list@mydomain.com Ex: MAIL list@mydomain.com me@mydomain.com
REALNAME	listname [address] {real name}	This command sets the real name value for "address" who is a member of list "listname" to the given value. The real name must be enclosed in { and } characters. Ex: REALNAME mdsupp@altn.com {Frank Thomas}
GET	catalog password magic-name	Retrieves a file from the specified catalog, MIME encodes it in an email message, and sends that message to the originating account or to the one specified in a RESULTS TO directive. Ex: GET utils pass myutil NOTE: The special PUBLIC catalog doesn’t require a catalog name or password in order to retrieve a file.
DIR	catalog	Retrieves a directory of the files and magic names available through the catalog. Ex: DIR public
See:

Remote Server Control Via Email

Account Access and Control

General Email Controls


General Email Controls

COMMANDS	PARMS	DESCRIPTIONS
HELP	none	A copy of the help.dat is processed and mailed back to the message originator.
RESULTS TO	address	The results of subsequent instructions are redirected to the email address specified rather than to that of the message originator. Ex: RESULTS TO someone@somewhere.com       LIST MDSUPP
STATUS	none	A status report on server operations and current conditions will be mailed back to the message originator.  Since the information contained in this status report is considered private the subject of the requesting message must contain the MDCONFIG Administrator level user and password such as:  Administrator, Password Ex: STATUS
MAIL FORMATS	none	A listing of all the supported mailbox formats will be mailed back to the originator. Ex: MAIL FORMATS
GET ADDRESS	none	MDaemon will send a message back to the originator which will contain the current machine name and IP address assigned to MDaemon’s computer.  This is useful when you want to find out the IP address assigned by your ISP when using a dynamic dial-up situation.   Since the information contained in this message is considered private the subject of the requesting message must contain the MDCONFIG Administrator level user and password such as:  Administrator, Password Ex: GET ADDRESS
See:

Remote Server Control Via Email

Account Access and Control

Mailing List and Catalog Control


MDaemon and Proxy Servers

MDaemon Server v3 has been purposely designed to be highly versatile. Consequently, it can be configured for use with a wide variety of network configurations and various other products. MDaemon’s flexibility allows it to work well with LAN proxy servers such as WinGate. To configure MDaemon to work through any proxy server, all you must do is make sure that the port settings (see Ports) you are using do not conflict with any that may be set in the proxy server itself. For example, SMTP email normally takes place on port 25. Since an IP address can only have a single port 25, two servers cannot both listen for SMTP email at the same time on the same machine. When attempting to integrate MDaemon with a proxy, it is recommended that whenever possible, you allow MDaemon as much control over mail processing and delivery as possible. To this end, SMTP and POP ports in the proxy should be disabled so that MDaemon can handle mail delivery independently.

However, should you find it necessary to channel mail through a proxy, MDaemon allows you to configure the ports which it will use to send and receive SMTP/POP/IMAP transactions.  You may need to set these ports to non-standard values in order to filter your SMTP/POP/IMAP transactions through a proxy server or firewall.

For more detailed information on configuring MDaemon to work with a proxy server, please consult the resources available at the following URL:

http://www.mdaemon.com/helpdesk/


Miscellaneous Information

•	If you send a message to "procnow@mydomain.com" MDaemon will generate the PROCNOW.SEM file.  As a result of this, you can’t use "procnow" as an email mailbox for one of your accounts.

•	Mail to domains listed in the LAN DOMAINS tab is kept in a directory called LNDOMAIN which stems off the LOCALQ directory.

•	If you send a message to "getaddress@mydomain.com" MDaemon will send a message back to you telling you the domain name and IP address that has been assigned to MDaemon’s computer.  This is useful if you want to know what IP address has been assigned to your computer from your ISP when you have a dynamic dial-up situation.


Semaphore Files

MDaemon responds to numerous semaphore files that can be used for a variety of useful purposes.  Periodically MDaemon will scans the \APP\ directory for the existence of these files.  If it finds one the associated behavior is triggered and the semaphore file is removed.  This provides for a simple mechanism which will allow administrators and/or developers to manipulate MDaemon without actually handling the interface.  The following is a list of all the semaphores and what they do:

FILENAME	ACTION
USERLIST.SEM	Forces MDaemon to reload the USERLIST.DAT file and rebuild the EVERYONE.GRP mailing list.  Use this when you make modifications to the USERLIST.DAT and need MDaemon to reload it.
EDITUSER.SEM	This semaphore is used to update specific records within the USERLIST.DAT file without a potentially time consuming complete rebuild.  To update a specific record within USERLIST.DAT you first construct a complete replacement record according to the format specified in the Technical Specifications section.  The new record will reflect the changes that need to be updated within USERLIST.DAT.  How does MDaemon know which record in USERLIST.DAT to update?   This is accomplished by prepending the new record with the original record’s email address followed by a comma.   The EDITUSER.SEM file can contain multiple records to update – each on its own line.  MDaemon will process the file one line at a time.  You can create EDITUSER.LCK to lock the file while you are updating it and MDaemon will not touch EDITUSER.SEM until EDITUSER.LCK is deleted.  To see a sample EDITUSER.SEM file open EDITUSER.SMP in your APP directory with a text editor.
ADDUSER.SEM	This semaphore creates new accounts.  It is used to force MDaemon to append new records to the end of the USERLIST.DAT file without causing a potentially time consuming complete rebuild of the user database.   Each line in this file must be a complete account record of the form specified in the Technical Specifications section.  Multiple new accounts can be specified – one account record per line.  MDaemon will process the file one line at a time and add each new account.  You can create ADDUSER.LCK to lock the file while you are updating it and MDaemon will not touch ADDUSER.SEM until ADDUSER.LCK is deleted.  To see a sample ADDUSER.SEM file open ADDUSER.SMP in your APP directory with a text editor.
PROCNOW.SEM	MDaemon will immediately go into mail processing mode.
PROCLOC.SEM	MDaemon will immediately go into mail processing mode and convert all RAW files, transact all local and LAN domain mail, and process any messages waiting in the MDaemon account’s mailbox.
PROCREM.SEM	MDaemon will immediately go into mail processing mode and transact all remote mail.
PROCDIG.SEM	Forces Digests to be sent immediately.
PROCRETR.SEM	Forces the Retry Queue to be processed.
PROCBAD.SEM	Forces the Bad Message Queue to be processed.
EXITNOW.SEM	MDaemon will terminate and remove itself from memory.
SCHEDULE.SEM	Forces MDaemon to reload the SCHEDULE.DAT file.
PRIORITY.SEM	Forces MDaemon to reload the PRIORITY.DAT file.
EXCPTION.SEM	Forces MDaemon to reload the EXCPTION.DAT file.
APPLYNOW.SEM	Causes the same action that occurs when you press the APPLY NOW button in the Primary Domain Setup screen.  This is required when changes are made to the port, domain name/IP or bind settings.
HANGUPR.SEM	Forces a "rude" hang-up of a connected RAS session.  This is an immediate and unconditional hang-up without regard to mail sessions which may be in progress across the connection so watch out!
HANGUPG.SEM	Forces a "graceful" hang-up of a connected RAS session.  MDaemon will wait for any pending mail sessions to close and will then hang-up the RAS session.
QUEUERUN.SEM	Just before a mail session begins MDaemon will create this semaphore file.  Inside the file will be a datestamp indicating the time and date of the most recent mail processing interval.
ONLINE.SEM	MDaemon will create this semaphore file once it makes a successful connection using RAS to the ISP.  MD will remove the semaphore once the connection has been terminated.  This is useful if you want to know when MD is using the RAS sub-system.
PREDIAL.SEM	MDaemon will create this file just before trying to use RAS/DUN.  This will allow other software to detect when it should free the dialup port so that MDaemon can use it.
POSTDIAL.SEM	MDaemon will create this file immediately after a connection made by MDaemon is taken down.
REBOOTMD.SEM	MD will reboot the tray icon and make the interface accessible.  This is useful if you are running MD as a service and the interface is not present.
FWUNLESS.SEM	Reloads the Forward Exception database.
DLUNLESS.SEM	Reloads the Delete Exception database.
DVUNLESS.SEM	Reloads the Delivery Exception database.
SUPPRESS.SEM	Reloads the suppressed address list for all domains.
MSGID.SEM	Forces a reload of the Dedupe value list.
GRPLIST.SEM	Reloads Mailing List names dynamically.
CATLIST.SEM	Reloads Catalog names dynamically.
WATCHDOG.SEM	MDaemon will check for and remove this semaphore from the APP directory at approximately 10-20 second intervals.  This file can be used by external apps to check if MDaemon is running.  If this file remains in the APP directory for more than 20 seconds, that is a good indication that MDaemon is no longer running.


Technical Specifications

Structure of USERLIST.DAT file

FIELD	LENGTH	NOTES
Domain	45	This is the domain the account is part of
Mailbox	30	This is the part left of the ‘@’ sign
FullName	30	This is the account’s first and last name
MailDir	90	This is the path to the directory where the account’s mail is stored
Password	20	This is the account’s password
AutoDecode	1	Set to ‘Y’ if the account is auto extracting attachments
IsForwarding	1	Set to ‘Y’ if the account is forwarding mail
AllowAccess	1	Set to ‘Y’ if the account is active
AllowChangeViaEmail	1	Set to ‘Y’ if the account can change options via email
KeepForwardedMail	1	Set to ‘Y’ if the account is retaining a copy of forwarded mail
HideFromEveryone	1	Set to ‘Y’ if the account is to remain hidden from EVERYONE list
EncryptMail	1	Set to ‘Y’ if the account is storing mail in an encrypted state
ApplyQuotas	1	Set to ‘Y’ if the account is subject to quota restrictions
EnableMultiPOP	1	Set to ‘Y’ if the account is actively using MultiPOP
LocalOnly	1	Set to ‘Y’ if account is restricted to sending local  messages only
MaxMessageCount	4	Max number of messages the account can have in the mailbox at once
MaxDiskSpace	6	Max disk space (in kilobytes) the account is allowed to consume
CR	1	Carriage return character
LF	1	Linefeed character
NOTES:

Due to the fact that MDaemon stores the passwords in an encrypted state the actual maximum length of a password is 12 characters.  MDaemon needs the remaining space to store the encrypted version of the password since it can be up to 8 characters longer than the unencrypted version.

It is possible to enter a plain unencrypted textual value into the password field manually and have MDaemon automatically encrypt it for you.  This will aid in third party development of userlist utilities since they will not have to worry about storing the password in an encrypted state.  To use this feature simply enter the textual password into the password field and set the last two characters of the password field (i.e.. positions 214 and 215) to a blank space and a "Y" character respectively.  When MDaemon reads the userlist file and encounters a password that has the last two characters arranged in this fashion it assumes that the value present in the field is a plain text entry that needs to be encrypted.

If an account is set to forward mail (i.e.. position 217 = "Y") then the forwarding address can be found in the FORWARD.DAT file under a section name that is the same as the account’s EMAIL field.

If encryption is being used (position 222 = "Y") then only messages which are smaller than or equal to 4096 bytes in length will be encrypted.  Messages larger than this will not be encrypted.


Creating an SMTP Session Policy Statement

More and more sites these days are announcing an up front policy regarding relaying of SMTP mail during the SMTP session itself.   If you would like to have MDaemon send a statement to the remote SMTP client when it attempts to send a message to your site you can do so by placing a text file called POLICY.DAT in the \app\ directory.  The content of this file will be sent to the remote SMTP client immediately after the SMTP greeting.  For example, a POLICY.DAT file with a statement regarding relaying of mail would look like this during the SMTP transaction:

220-Alt-N Technologies ESMTP MDaemon v3

220-This site does not authorize you to relay mail.

220-If you are not an authorized user of our domain’s mail

220-server you must

220-not relay mail through this site.

220

HELO domain.com

and so on...

The POLICY.DAT file must be comprised of printable ASCII text only and have no more than 512 characters per line;  however no more than 75 characters per line is highly recommended.   The maximum size of this file is 5000 bytes.  MDaemon will not display files larger than 5000 bytes.  Each line within this file must start with "220-" except the last line which must start with "220 " (note that the dash is missing on the last line and is replaced with a blank space).

For example:

C:\MDAEMON\APP>Copy con POLICY.DAT

220-This site does not authorize you to relay mail.

220 So don’t do it!

^Z

See:

Customizing SMTP and POP Protocol Strings

SMTP String Codes

POP String Codes


Customizing SMTP and POP Protocol Strings

MDaemon contains a mechanism for altering the SMTP and POP protocol strings that it uses.  You can provide custom strings for most of the SMTP and POP dialog.  Each string that MDaemon uses has a unique number and a specific default value.  These defaults will be used unless a custom string is found in the [Custom-SMTP] or [Custom-POP] sections in the MDAEMON.INI file.

When creating custom SMTP strings, pay close attention to the following:

1.	Some SMTP default strings start with a blank space character (See SMTP String Codes). Any replacement for these strings must also start with a blank space character. Failure to do so will result in server failure!

2.	You must enclose the custom string in quotation marks when you place it into the mdaemon.ini file. Failure to do so will result in server failure!

3.	Some strings contain macros such as "%s" or "%d".  These macros are dynamically filled in with data when the string is loaded and used.  Custom strings are not required to use these macros.  However, a custom string may duplicate these macros provided they are placed in the same sequence as they appear in the default string. Failure to place macros in the same sequence within a custom string will result in instant server failure!

When creating custom POP strings, pay close attention to the following:

1.	All POP default strings start with either "+OK" or "-ERR" (see POP String Codes). Any replacement for these strings must also start with "+OK" or "-ERR". Failure to properly use "+OK" or "-ERR" text at the start of a custom string will result in server failure!

2.	Some strings contain macros such as "%s" or "%d".  These macros are dynamically filled in with data when the string is loaded and used.  Custom strings are not required to use these macros. However, a custom string may duplicate these macros provided they are placed in the same sequence as they appear in the default string. Failure to place macros in the same sequence within a custom string will result in instant server failure!

Here is a list of the unique numbers and default string values used by MDaemon. Only the following strings can be changed. Attempting to change a string that is not listed here will result in server failure!

See:

SMTP String Codes

POP String Codes

Creating an SMTP Session Policy Statement


SMTP STRING CODES

7000="%s ESMTP service ready [%d]"

7002="%s Hello %s, pleased to meet you"

7004="<%s>, Sender ok"

7062="<%s>, Sender ok (alias for %s)"

7006="<%s>, Recipient ok"

7008="<%s>, Recipient ok (alias for %s)"

7010="Enter mail, end with <CRLF>.<CRLF>"

7011="See ya in cyberspace"

7012="What? I don’t understand that."

7013="Ok, message saved"

7014="%s is not a valid maildrop.  Please check the address and try again."

7015="Sorry, try later.  Can’t create temporary mail file. :("

7016="RSET?  Well, OK."

7017="Why is there an NOOP instruction?"

7018="Yeah, I know that one.  He (or she) is %s <%s>."

7019="<%s>?  Never heard of ‘em."

7020="<%s>?  There’s more than one possible match to that query on this server."

7021="Yeah, there’s a list here by that name.  Mail to <%s>."

7022="<%s>?  There’s no mailing list here by that name."

7023="<%s>?  There’s more than one possible match to that query on this server."

7024="Hey!  I don’t let remote systems TURN on me."

7025="Help system currently inactive."

7033="%s Hello %s, did you know your name is really %s?"

7034="Unexpected command or sequence of commands."

7037="Sorry, SMTP server too busy right now (%d).  Try again later."

7038="SMTP session successful, %ld bytes transferred!"

7039="SMTP session abnormally terminated, %ld bytes transferred!"

7041="Sending <%s> to [%s]"

7042="Connection timed out!"

7043="Spooling mail to default gateway"

7044="This server does not accept routed mail"

7046="Node <%s> does not store mail here"

7047="Your IP address <%s> does not have access to node <%s>"

7048="No messages waiting for node <%s>"

7050="<%d> pending messages for node <%s> started"

7051="Unable to queue message for node <%s>: Internal processing error"

7052="This server configured to NOT honor EHLO at present."

7053="Sorry, <%s> is not allowed access from your location"

7055="<%s>, Sender unknown"

You can see from the table that the initial SMTP greeting string is coded 7000. Therefore to create a custom SMTP greeting string place the following entry into the MDAEMON.INI file:

[Custom-SMTP]

7000=" Alt-N Technologies ESMTP server"

Note that you must enclose the custom string in quotations. Note also that this example string does not use any %s macros like the default one does.  This is fine.

See:

Customizing SMTP and POP Protocol Strings

POP String Codes


POP STRING CODES

7200="+OK %s POP service ready [%d]"

7201="+OK %s... Recipient ok"

7235="-ERR Access denied.  Contact postmaster@%s for more information."

7234="-ERR sorry, POP server too busy right now.  Try again later."

7202="-ERR sorry, there’s no mailbox for %s here"

7203="-ERR that command is valid only in the AUTHORIZATION state!"

7204="-ERR that command is valid only in the TRANSACTION state!"

7205="-ERR that command is valid only in the UPDATE state!"

7233="-ERR maildrop already locked"

7206="+OK %s... see ya in cyberspace"

7207="-ERR access denied"

7208="+OK %s’s mailbox has %d total messages (%ld octets)."

7210="+OK %d messages (%ld octets)"

7219="-ERR no such message"

7220="-ERR no such message, only messages 1 thru %d are present in your inbox"

7222="+OK %s %s POP Server signing off (mailbox empty)"

7223="+OK %s %s POP Server signing off (%d messages left)"

7214="-ERR unknown POP command!"

7213="+OK message %d deleted"

7224="-ERR message %d already marked for deletion"

7216="Sending TOP of message %d (unbuffered operation…)"

7241="Sending <%s> to [%s]"

7242="Connection timed out!"

7243="Transmission Complete <%s>"

7247="Message %d (%ld bytes) exceeds max message size limit of %ld bytes"

7248="Collecting Message %d (%ld bytes) would exceed account’s max disk space limit of %ld bytes"

7249="Collecting Message %d would exceed account’s max stored message limit of %ld"

7237="POP session complete, %ld bytes transferred!"

7238="POP session timed out, %ld bytes transferred!"

See:

Customizing SMTP and POP Protocol Strings

SMTP String Codes


Route Slips

The concept of a "route slip" has been present in MDaemon since the beginning but has never been documented.  Typically, a message file that is waiting in a queue contains within itself all the information that is needed to get the message delivered to the proper location.  There are headers stored within the .MSG file (such as the X-MDaemon-Deliver-To header) which provide MDaemon with instructions as to where and to whom the message should be delivered.  Sometimes however it is necessary or useful to override this information and provide specific alternatives to where and to whom an .MSG file must be sent.  The route slip provides just such a mechanism.  A route slip is a file which provides MDaemon with very specific instructions as to where and to whom a message file should be sent.  If a route slip is present for a particular message file then the settings within the route slip - and not those within the .MSG file itself - control where and to whom the message is sent.

Route slips end with the extension .RTE.  For example, if a message file waiting to be sent is called MD0000.MSG then the corresponding route slip file for this message will be called MD0000.RTE and must be located in the same directory (mail queue) as the message file.

The format of a route slip is as follows:

[RemoteHost]

DeliverTo=remote-domain.com

This section of a route slip provides MDaemon with the server to which the corresponding .MSG file is to be sent.  MDaemon will always attempt a direct connection to this host attempting to route the message in as short a time as possible.  Only one host may be specified.

[RemoteHost]

IgnoreRcptErrors=Yes (or No)

It is possible to specify an unlimited number of recipients of the .MSG file being sent.  Sometimes hosts might refuse a particular address to which you are attempting to send a copy of the message.  Ordinarily under SMTP regulations the session should be aborted.  This switch will allow MDaemon to proceed to the next recipient in the list without aborting the session completely.

[Port]

Port=xxx

This switch specifies the port that the TCP/IP connection and delivery attempt should be made on.  25 is the default for SMTP email.

[LocalRcpts]

Rcpt0=address@my-domain.com

Rcpt1=other-address@my-domain.com

Rcpt2=yet-another-address@my-domain.com

[RemoteRcpts]

Rcpt0=address@foreign-domain.com

Rcpt1=other-address@foreign-domain.com

Rcpt2=yet-another-address@foreign-domain.com

These sections of the route slip allow you to specify any number of local and remote recipients who should receive a copy of the associated .MSG file.  Local and remote recipient addresses must be kept separate and placed in their corresponding [LocalRcpts] and [RemoteRcpts] sections.

Route slips provide a good mechanism for delivering or redirecting email but they are not generally necessary.  One use that MDaemon makes of route slips is in the case of "routed" mailing list mail.  When you have a mailing list that is set to route a single copy of the list message to some remote host a route slip is employed to accomplish this.  It is a very efficient method of mail delivery when you have bulk addresses to deliver mail to since only a single copy of the message is required while any number of recipients of the message can be specified.  Not all remote hosts allow this sort of routing to occur however.  Since it is ultimately they who will have to deliver a copy of the message file to each address some hosts place an upper limit on the number of recipients they will allow you to specify.


MDaemon Technical Support

Technical Support for the MDaemon Server is provided by MDaemon’s publisher Deerfield.com and is offered on several different levels, outlined below. Please review the support options and select whichever is appropriate for your needs.

All of the following options are located and fully discussed at the MDaemon web site.

http://www.mdaemon.com

Telephone Support for All Users

MDaemon Technical Support is available via telephone for a flat rate, per incident fee of $59.95. Paid telephone support is available between the hours of 9:00am and 5:00pm, Eastern Standard Time, Monday through Friday (excluding holidays), at (517) 731-9200. When calling, please have credit card information and product license number ready.

Free Technical Support Options

Support for all users is provided via the MDaemon Help Desk and the MDaemon Open Discussion Forum, which allows for dialog within a threaded, searchable, and intuitive forum environment.

•	MDaemon Help Desk— http://www.mdaemon.com/helpdesk

The MDaemon Help Desk outlines a number of resources to help you learn more about MDaemon, troubleshoot problems, and so on.  By utilizing the Help Desk you can often avoid the need to contact Technical Support. The MDaemon Help Desk contains a number of useful resources including:

MDaemon Knowledge Base— You can search our support database for answers to your questions. With support for time-based, natural language, and article-based searching, plus a listing of Frequently Asked Question, you’re sure to find the right answer!

Helpful Articles— The Help Desk contains a number of useful articles addressing various MDaemon configuration issues and other related topics.

Free Add-on & Complimentary Software— Here you can download free supplementary software and utilities written by MDaemon’s developers and users.

•	MDaemon Support Mailing List— The MDSupp email discussion group is a mailing list hosted by Alt-N Technologies. It is an open membership list where users can get help and discuss MDaemon with other users. MDaemon’s Development Team, other support staff, and a large mix of MDaemon users regularly participate in the discussion and contribute feedback and help. Odds are that someone will have an answer to your MDaemon question in the MDSupp email group. To join MDSupp, send a message to JoinMDSupp@altn.com and you will automatically be added to the list.

•	MDaemon Open Discussion Forum— Come join in the MDaemon Open Discussion Forum to get help on your questions from both the MDaemon Tech Support Staff and other MDaemon users. It’s a great way to learn, share, and exchange ideas!  The Forum allows for dialog within a threaded, searchable, and intuitive forum environment. It is located at  http://forum1.deerfield.com/~mdaemon/

•	Free Email Support for All Users— Free Unlimited Email Support is available for all MDaemon users.  To obtain this free support via email, please submit your technical support request using the Technical Support Request Form located at:

http://www.securecc.com/mdaemon/techpur.htm

The Technical Support Request Form can also be reached via link from the mdaemon.com web site.

Reseller Purchase

Users who purchased their copy of MDaemon from an Official Deerfield.com Reseller will be referred back to them for support. If you would like to receive technical support from Deerfield.com, you will be required to pay the telephone support charge of $60.00 USD per hour billed in 10-minute increments.  For information about Official Deerfield.com Resellers, or to locate a reseller near you visit:

http://www.securecc.com/windealers/index.cfm

Sales and Reseller Inquiries

Sales questions (of a non-technical nature) relative to MDaemon software should be directed to <sales@mdaemon.com>. Alternatively, you can call Deerfield.com at (517) 732-8856.


Contacts

MDaemon, WorldClient, and RelayFax are trademarks of Alt-N Technologies, LTD.

Alt-N Technologies, LTD.

1179 Corporate Drive West, Suite #103
Arlington, TX 76006
www.altn.com

MDaemon Server Version 3 is published by:

Deerfield Communications Inc.

4241 Old U.S. 27 South
P .O. Box 851
Gaylord, MI 49735
517.732.8856
517.731.2642 fax
deerfield.com

Sales and Reseller Inquiries

Sales questions (of a non-technical nature) relative to MDaemon software should be directed to <sales@mdaemon.com>.  Alternatively, you can call Deerfield.com at (517) 732-8856.

You can locate an MDaemon reseller near you by using the deerfield.com Global Reseller Database located at:

http://www.securecc.com/Windealers/index.cfm

Documentation Issues

mdaemon-docs@altn.com

MDaemon Beta Testing

Alt-N Technologies maintains an open policy on Beta-team participation. If you would like to join Alt-N’s Beta-test Team and receive advance beta-copies of future MDaemon releases, Service Packs, and other Alt-N software, simply send a message to BetaJoin@altn.com. Our system will return to you an information packet with instructions for obtaining Beta software and participating in Beta testing. For more information on the MDaemon BetaTeam visit:

http://www.altn.com/betateams.html

Note
The BetaTeam is for those who wish to acquire Alt-N software before its general release and aid in its testing; it is not a technical support alternative. Technical support for MDaemon will only be provided through those methods outlined in the MDaemon Technical Support section. If you would like to subscribe to the MDaemon support Mailing List hosted by Alt-N Technologies, send a message to JoinMDSupp@altn.com and you will be automatically added to the list.


Session transcript

This window displays all session i/o.


Remote host/IP

This window tells you the name and IP address of the remote computer MDaemon with which MDaemon is interacting.


Message from/to

This window displays the sender's address and the address of the intended recipients.


Message transfer statistics

This keeps a running total of the number of bytes transmitted to or collected from the remote system, the percentage completed, and the current speed of the transfer.


Inactivity timeout

This counter displays how much inactivity time is left before MDaemon will close the session.


Disconnect

This button will immediately disconnect the server from the remote system.


Run WorldClient server using this TCP port

This this the port on which WorldClient will listen for connections


Domain name

Enter your primary domain name here. This is the default domain name used when creating new accounts. It is also used in the WorldClient accounts that are created automatically when you are utilizing the MDaemon/WorldClient Pro Integration features. Typically, the value entered here will be the registered Internet domain name that a DNS server resolves to the IP address of the local machine running the server, or a qualified alias of that name.

Alternatively, you may choose to use a fictitious domain name for your Primary Domain Name (such as "company.mail") in some situations.  When configuring your server in this way it may be necessary to use the Header Translation feature, and/or the Domain Name Replacement Engine, to enable proper mail distribution.


HELO domain

This Domain name will be used in the SMTP HELO/EHLO instruction when sending mail. In most cases, this will be your Primary Domain Name.


Domain IP

This is the Primary Domain’s IP address.


Bind listening sockets to this IP only

Selecting this switch causes MDaemon to bind its listening network sockets using the specific IP address found in the Domain IP text box.  Ordinarily, this control will only need to be used in certain circumstances when hosting multiple domains.

For more information on this type of configuration, see:

Hosting Multiple Domains


ISP/gateway host's IP or domain name

Specify your mail gateway’s host name or IP address here.  This is generally the SMTP server on your ISP.

Note
Do not enter MDaemon’s Primary Domain Name or IP address into this text box.  This entry should be an Internet gateway host other than yourself that can relay mail for you.


Send every outbound email message to the gateway host

Select this option if you want all outbound email, regardless of its destination domain, to be spooled to a gateway host for routed delivery. If selected, all outbound email will be sent to the host specified in the ISP/gateway host’s IP or domain name field. Typically, this feature is useful during high volume periods when direct message delivery would result in an excessive taxation of server resources.


Send only undeliverable outbound mail to this host

Click this option if you want to spool only undeliverable outbound email to the gateway host specified in the ISP/gateway host’s IP or domain name field. Undeliverable mail is email destined for hosts that could not be resolved to an actual IP address (such as an unregistered gateway to a remote network) or email destined for a host that was resolved properly but could not be connected to directly or is refusing direct connections. Rather than return such mail to its originator, this option causes MDaemon to pass the message off to a more powerful MTA. Sometimes the mail system run by your ISP may have routed methods of mail delivery to which your local server may not have direct access.


Attempt to send all mail direct without using an intermediate host

When this option is chosen, MDaemon will attempt to deliver all mail itself instead of passing it to another host. MDaemon will place undeliverable messages into its Retry System and continue to attempt to deliver them according to the parameters and time intervals that you set in the Retry Configuration dialog. You can access this dialog by clicking the Retry Queue Settings button.


My ISP requires me to log in before sending mail

As a security measure, in order to prevent unauthorized users from attempting to relay mail through their servers, some ISPs require their customers to authenticate themselves via ESMTP AUTH or by first performing a POP check of their email account. If this is the case for your ISP, you can open the AUTH/POP before SMTP dialog by clicking this button. There you can enter the required authentication information.


Retry queue settings

Click this button to open the Retry Configuration dialog from which you can designate how often MDaemon will attempt to deliver messages which it has thus far been unable to deliver. You can also specify a time interval after which the attempts will cease, and what to do with these messages after the final attempt is made.


Keep message in the primary queue for at least xx minutes

This setting governs the length of time a message will remain in the primary queue before being removed and placed in the retry queue.  The primary queue will generally attempt to deliver the message quicker and more frequently than the retry queue.


Retry sending undeliverable mail once every xx minutes

This setting determines how frequently the messages in the retry queue are processed.


Inform the sender when message is placed in retry queue

This switch will inform the sender when his/her message is removed and placed in the retry queue.  The text of this message can be found (and edited) in the DELWARN.DAT file.


Inform the sender when subsequent delivery attempts fail

If a delivery attempt of a message in the retry queue fails, a message explaining this fact will be dispatched to the sender of the message.  The text of this message can be found (and edited) in the DELWARN.DAT file.


If a message is still undeliverable after xx days then:

This setting determines the number of days that a message can remain in the retry queue before being removed.


Place the undeliverable message in the bad message queue

Once a message has reached the time limit set in the If A Message Is Still Undeliverable After xx Days Then: control, a copy of that message will be moved to the bad message directory if this switch is enabled.


Inform the sender that the message could not be delivered

Once a message has reached the time limit set in the If A Message Is Still Undeliverable After xx Days Then: control, this switch will cause MDaemon to send a message to the sender informing them that the message has been permanently removed from the server. The text of this message can be found (and edited) in the DELERR.DAT file.


Inform the postmaster that the message could not be delivered

If this switch is enabled, the postmaster will be notified when a message has been permanently removed from the retry system.


. . . Unless it's an MDaemon auto-generated message

The retry system will never inform MDaemon when an auto-generated message fails to be delivered. However, because such information may be useful to the postmaster, he or she will be informed when these messages cannot be delivered. Click this checkbox if you do not want the postmaster to be informed when auto-generated messages cannot be delivered. Examples of auto-generated messages are return-receipt notifications, auto-responder generated messages, results of account processing, and so on.


Just before processing the (local/remote) mail queue run this program

This field specifies a program path and name that will be executed just prior to the processing and delivery of any RFC-822 messages that might be in the local or remote message queues. If complete path information is not provided, MDaemon will first search for the executable in the MDaemon directory, then in the Windows System directory, next in the Windows directory, and finally the directories listed in the PATH environment variable.


. . . Suspend all operations for xx seconds

The value entered here determines how MDaemon will behave while the specified program is in progress. MDaemon can be configured to pause its execution thread for the number of seconds specified while waiting for the process thread to return. If the process returns before the number of seconds has elapsed, MDaemon will resume its execution thread immediately. Enter the numeral zero in this control and MDaemon will not suspend operations at all. Entering “-1” will cause MDaemon to wait until the process returns, no matter how long that might be.


Don't execute when queue is empty

Enable this switch if you do not want the specified program to run when the queue is empty.


Force process to terminate

Sometimes the process you need to run may not terminate on its own. This switch will cause MDaemon to force the session to terminate once the time specified in …Suspend All Operations For XX Seconds has elapsed. This switch does not work if the elapsed time interval is set to “-1”.


Run process in a hidden window

Click this checkbox if you want the process to run in a hidden window.


Signal ISP to dequeue waiting mail

When it is time to process remote mail MDaemon can connect to any server on any port and send any string that you wish to send. This is useful when you need to signal a remote server to release your mail by sending some string to them. For example, ATRN, ETRN, or QSND. You can also use this feature when a FINGER or TELNET session is briefly required in order for your ISP to determine that you are online.


Send signal once every [xx] times remote mail is processed

By default the dequeue signal will be sent each time that remote mail is processed. Entering a number into this control will prevent the dequeue signal from being sent every time. It will be sent every x number of times as designated. For example, setting this value to "3" would cause the signal to be sent every third time that remote mail is processed.


Send signal to this remote host

This is the host to which you wish to connect to signal the release of your mail.


Use this TCP port

Enter the port on which you wish to make the connection. The default is 25 (the SMTP port), which is appropriate for the ETRN or QSND signaling method. Port 366 is typically used for ATRN, and port 79 is used for FINGER.


Send this string to host

This control is for specifying the text string that needs to be sent in order for your mail to be released. For example, the ETRN method requires the text "ETRN" followed by the domain name of the site being queued. Other methods require different text to be sent.  Consult your ISP if you need more information on what to send to unlock your mail queue.

Note
When using a dequeue method of mail hosting, we recommend using On-Domain Mail Relay (ODMR) whenever possible. We believe that it is currently the best method available for hosting your email in this manner. ODMR requires the ATRN command to be used in this control.


Send SMTP "EHLO" Before Transmitting String To Host

If you enable this checkbox then you should be connecting to an SMTP server to signal release of your mail. This switch causes an SMTP session to be initiated with the specified host and allows the session to progress just beyond the SMTP "EHLO" stage before sending the unlock string.


Hide dequeue session windows while they are in progress

Click this checkbox if you want to hide sessions windows while they are in progress.

Note
If the value you enter into the Send Signal To This Host control is a domain name and not an IP address, MDaemon will perform an MX record resolution of this site in an attempt to connect to the site’s MX IP address. This assumes you have the MX resolution engine switched on and working (see DNS). If the value entered is an IP address and not a domain name then the connection will be made using that IP address.


I must authenticate before sending the dequeue signal (required for ATRN)

As a security measure, in order to prevent unauthorized users from attempting to dequeue their customers email, some ISPs require their customers to authenticate themselves via ESMTP AUTH before sending the dequeue signal. If this is the case for your ISP, you can open the Dequeue AUTH dialog by clicking this button. There you can enter the required authentication information.

Note
Authentication is required when using the ATRN command to dequeue your email.


On-Demand Mail Relay (ODMR)

We believe that the best relay (queue/dequeue) method currently available for hosting your email is On-Demand Mail Relay (ODMR). This method is superior to ETRN and other methods in that in requires authentication before mail is dequeued. Further, it utilizes a new ESMTP command called ATRN that does not require the client (customer) to have a static IP address because it immediately reverses the flow of data between the client and server (provider) and despools the messages without having to make a new connection to do so (unlike ETRN).

MDaemon fully supports ODMR on the client side via using the ATRN command and authentication controls on the Dequeue tab, and on the server side using the Gateway Domain features on the ATRN / AUTH tab of the Gateway Domains Editor.

Many mail servers do not yet support ODMR therefore you should check with your provider before attempting to use it.


RAW formatted mail is picked up from this directory

Enter the directory path where MDaemon Server v3 should expect to find RAW format messages that are to be processed and entered into the mail stream. This directory is scanned at each local mail processing interval for RAW mail, which the server then converts to RFC-822 and delivers to its intended recipient(s).

For a complete discussion of RAW message specifications see:

RAW Message Specifications


Bad messages (parsing errors, unknown  users, etc) are placed here

Enter the directory path where bad messages should be placed. The bad message queue will contain messages destined for unknown yet supposedly local users, and messages that cause parsing problems.


When collecting inbound mail, work files should be stored here

Enter the directory path where MDaemon should store incoming transient SMTP mail messages. This work directory is used only while an SMTP session is in progress. While a session is ongoing, the messages being delivered to the server are stored in temporary files in this directory.


RFC-822 compliant remote message queue (non-local mail only)

Enter the directory path that MDaemon should use as the outbound mail queue. This directory will contain only processed RFC-822 format messages that are waiting for delivery to their final destination or to the mail gateway. All mail placed in this directory must be RFC-822 compliant and have an extension of MSG in order to be processed by MDaemon. Mail in this queue is destined for domains hosted by other servers.


RFC-822 compliant local message queue (local mail only)

Enter the directory path that MDaemon should use as the local mail queue. This directory will contain only processed RFC-822 format messages that are waiting for delivery to their final destination or to a mail gateway. All mail placed in this directory must be RFC-822 compliant and have an extension of MSG in order to be processed by MDaemon. Mail in this queue is destined for local mailboxes.

If you are using the LAN Domains feature, messages destined for other servers on your local LAN will be stored in a subdirectory of the this Local Message Queue called Lndomain.

See:

LAN Domains


Mailing list digests are stored here while waiting to be queued

Enter the directory path where MDaemon should store Digest mail waiting to be queued for delivery.


Mailing list digests are archived here

Enter the directory path where MDaemon should Archive Digests.


Log transcript files are stored here

Enter the directory where transaction and event logs are stored.


Archive a copy of all inbound/outbound mail

This switch enables the archival engine. Activating it will cause a copy of every inbound and outbound message that passes through the server to be sent to the address(es) specified in the control following.


Send a copy of every inbound/outbound message to these addresses

Enter one or more addresses to which you wish to send archival messages. Multiple addresses must be separated by a comma. You may specify Local and Remote addresses and Address Aliases.


Include MDaemon mailing list messages in the archive also

Select this switch if you want archived mail to include your mailing list messages.


Include MultiPOP collected mail in the archive also

Select this switch if you want archived mail to include messages collected through MDaemon’s MultiPOP feature.


Label archive messages with "(archive copy)" in message subject

Enable this switch if you want to include “(Archive Copy)” in the Subject: header of archived mail.


Listen for inbound SMTP events on this TCP port

MDaemon will monitor this port for incoming connections from SMTP clients.


Create outbound SMTP events using this TCP port

This port will be used when mail is sent to other SMTP servers.


Listen for inbound ODMR events using this TCP port

MDaemon will monitor this port for incoming On-Demand Mail Relay (ODMR) connections such as ATRN from Gateway Domains.


Listen for inbound POP3 events on this TCP port

MDaemon will monitor this port for incoming connections from remote POP clients.


Create outbound POP3 events using this TCP port

This port will be used when mail is retrieved from POP3 servers.


Listen for inbound IMAP events on this TCP port

MDaemon will monitor this port for incoming IMAP requests.


Query DNS servers using this UDP port

Enter the Port you want MDaemon to use for sending and receiving data grams to the DNS server.


LDAP port for database & address book posting

MDaemon will post database and address book information to your LDAP server on this port.

See: LDAP Address Book Support


Listen for MDConfig connections on this TCP port

This is the port that MDaemon will monitor for MDConfig connections.


Listen for WebConfig connections on this TCP port

This is the port that MDaemon will monitor for WebConfig connections.


Return port settings to defaults

This button returns all the port settings to their standard values.


Bind to new port values now

When you alter the values of any of the port settings you will need to press this button to have your changes take immediate effect. Otherwise, your changes will not be put into place until the next time the server is started.


Try to use DNS servers defined in Windows TCP/IP settings

Windows sometimes keeps a DNS server IP address in the local TCP/IP configuration. If this is the case on your computer then you can check this option. If MDaemon cannot find a locally maintained DNS server it will continue on and use the ones specified on this screen.


Primary DNS server IP address

Enter the IP address of the DNS server that you want MDaemon to query for ‘A’ and ‘MX’ records. In order to ensure proper operation this entry must be specified.


Backup DNS server IP address

Enter the IP address of the backup or secondary DNS server that you want MDaemon to query for ‘A’ and ‘MX’ records. This entry is optional but recommended.


Retry failed lookup attempts this many times

If for some reason a lookup attempt fails, this is the number of times that MDaemon will repeat the attempt. If you have designated a backup DNS server, both servers will be included in each lookup attempt.


Query DNS servers for MX records when delivering mail

Enable this control if you want MDaemon to query your designated DNS servers for ‘MX’ records when it is attempting to deliver mail.


Use `A' record IP addresses found within MX record packets

Click this checkbox if you want MDaemon to attempt delivery to ‘A’ record IP addresses when such are discovered during ‘MX’ record processing.


Send message to next MX host when an SMTP error occurs

With this function active, MDaemon will continue to attempt message delivery to the next ‘MX’ hosts even if the current ‘MX’ returns a fatal SMTP error.


Immediately return mail when DNS says domain does not exists

This switch will cause MDaemon to immediately return a message if a DNS lookup returns a “Domain Does Not Exist” message.  This will prevent this sort of mail from needlessly going into the delivery retry cycle.


Hosts File
Hosts file…

Before querying the DNS servers, MDaemon will first attempt to resolve an address by processing the Windows HOSTS file. If this file contains the IP address of the domain in question, MDaemon will not need to query the DNS server.

Note
You must enter the complete path and filename rather than just the filename.  MDaemon will attempt to use the following values as the default location of this file:

Windows 95/98 - [drive]:\windows\hosts
Windows NT - [drive]:\windows\system32\drivers\etc\hosts

The HOSTS file is a Windows file that contains the A-record or primary IP address for a domain name. MDaemon also allows you to specify MX-record IP addresses within a file called MXCACHE.DAT. This file can be found within the MDaemon\APP\ subdirectory. Load the MXCACHE.DAT file into a text editor and read the comments at the top of the file for more information.


Edit MXCACHE file

Click this button to view or edit the MXCACHE.DAT file with MDaemon’s text editor.


Edit hosts file

Click this button to view or edit the HOSTS file with MDaemon’s text editor.


Wait XX seconds for sockets to connect before giving up

After initiating a connection request MDaemon will wait this many seconds for the remote system to accept the connection. If the remote system does not respond within this time frame MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.


Wait XX seconds for protocol dialog to start before giving up

Once a connection has been established with a remote host, this is the number of seconds that MDaemon will wait for the remote host to begin the SMTP or POP3 protocol dialog.  If the remote host does not begin the protocol session within this time frame MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.


Wait XX seconds for MX DNS server responses

While using DNS services to resolve ‘MX’ hosts for remote domains, MDaemon will wait for responses to its ‘MX’ queries for this number of seconds. If the DNS server does not respond within this time frame MDaemon will attempt to deliver the message to the IP address specified in the remote host’s ‘A’ DNS record. If that attempt fails MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.


Wait XX seconds for A-record DNS server responses

This timer governs how long MDaemon will wait while attempting to resolve a remote host’s IP address. If the attempt fails, MDaemon will send the message to either the Gateway Host or Retry Queue depending upon which option you have chosen on the Domain/ISP tab of the Domain Configuration Editor.


SMTP and POP sessions timeout after XX inactive minutes

If a successfully connected and operating session remains inactive (no i/o) for this length of time, MDaemon will abort the transaction. MDaemon will try again at the next scheduled processing interval.


IMAP sessions timeout after XX inactive minutes

If an IMAP session has no activity for this number of minutes, MDaemon will close the session.


IMAP NOOP commands trigger 1 minute inactivity timeout

When this checkbox is enabled, the IMAP inactivity timer will be set to one minute when a NOOP command is encountered. Some IMAP clients will issue NOOP commands simply to keep sessions open even though there is no actual mail transaction activity going on. This feature will prevent such sessions from remaining active and thus will reduce resources consumed, which can be extremely useful for higher volume IMAP based mail sites.


Maximum message hop count (1-100)

RFC standards stipulate that a mail server must stamp each message each time that it is processed. These stamps can be counted and used as a stopgap measure against recursive mail loops that can sometimes be caused by errant configurations. If undetected, these looping message delivery cycles will consume your resources. By counting the number times the message has been processed, such messages can be detected and placed in the bad message directory. The assumption is that if a message hasn’t reached its recipient after being processed by a given number of mail servers then there is probably a mail loop in progress. Most likely, the default setting of this control should be sufficient to prevent mail loops and will not need to be changed.


Latency - XX milliseconds

This is the delay in milliseconds between POP/SMTP/IMAP protocol commands. This is useful for preventing high-speed connections from processing data faster than the recipient can extract it. This delay takes effect only during the POP/SMTP/IMAP protocol command sequence – the actual transfer of a mail message file is already fully buffered.


Maximum concurrent SMTP outbound session threads

The value entered here represents the maximum possible outbound SMTP session threads that will be created when it is time to send outbound mail. Each session thread will send outbound messages until either the queue is empty or the Max SMTP Outbound Messages Spooled Per Thread setting has been reached. For example, if the outbound mail queue has twenty messages waiting when it is time to send mail and the value of this setting is five, then five session threads will be simultaneously created and each will consecutively deliver four messages.

You should experiment with the number of session threads that yield the best performance for your bandwidth.  It is possible to specify so many threads that your bandwidth will be overloaded or your Windows machine will run out of resources and you will lose delivery efficiency. Remember, each SMTP session thread created by MDaemon will deliver messages consecutively and therefore four threads delivering two messages each might perform better and faster than eight threads delivering only one message each. A good place to start would be five to ten threads when using a 28.8k modem and ten to fifteen for ISDN.


Maximum SMTP outbound messages spooled per thread

This setting places a limit on the number of individual messages that each session thread will send before it stops delivering mail and frees itself from memory. Ordinarily, you should leave this control set to zero, which will cause each session thread to continue delivering messages until the queue is empty.


Maximum concurrent SMTP inbound session threads

This value controls the number of concurrent inbound SMTP sessions threads that the server will accept before it begins responding with a “Server Too Busy” message.


Enable SMTP expansion threading

When this setting is enabled, MDaemon will continue processing other sessions while cracking large mailing list messages that arrive via SMTP.


Maximum concurrent POP outbound session threads

The value entered here represents the maximum possible outbound POP session threads that will be created when it is time to collect DomainPOP and MultiPOP mail. Each session will collect this type of mail until all DomainPOP and MultiPOP servers have been processed, and all mail has been collected. For example, if there are fifteen MultiPOP sessions amongst all of your users and the value of this setting is set to three, then each session thread will collect mail from five MultiPOP sources.

You should experiment with the number of session threads to determine what number will yield the best performance for your bandwidth. It is possible to specify so many threads that your bandwidth will be overloaded, or your Windows machine will run out of resources and you will lose processing efficiency. Remember that each POP session thread created by MDaemon will collect mail until all sources have been exhausted. Therefore, four threads collecting mail from twenty sources might perform better and faster than twenty threads collecting from a single source. A good place to start would be two to five threads with a 28.8 modem and five to ten for ISDN.


Maximum concurrent POP/IMAP inbound session threads

This value controls the maximum number of concurrent POP and IMAP inbound mail sessions that the server will accept before it begins responding with a “Server Too Busy” message.


Enable POP3 expansion threading

When this setting is enabled, MDaemon will continue processing other sessions while cracking large mailing list messages that arrive via DomainPOP.


Route message back to sender

Messages that arrive at the server destined for unknown yet supposedly local users will be returned to the message originator if this option is activated.


Send message to the "postmaster" user

Messages that arrive at the server destined for unknown yet supposedly local users will be forwarded to whatever user has been aliased as the postmaster.


Place message in bad message directory

Messages that arrive at the server destined for unknown yet supposedly local users will be routed to the bad message directory.


Enable advanced options

Click this checkbox to enable the following advanced mail routing properties.


Send the message to this host

If a mail host is specified here, messages addressed to unknown local users will be sent to it.


Use this address in SMTP envelope

This address will be used in the SMTP “Mail From:” statement used during the session handshaking with the accepting host. Normally the sender of the message is used in this portion of the SMTP envelope. If you require an empty command (MAIL FROM <>) then enter “[trash]” into this control.


Use this TCP port

MDaemon will send this message on the TCP port specified here rather than the default SMTP outbound port.


Domain list

This window contains the list of your secondary domains. This list has three columns: Domain Name—which lists the name of the each domain, IP—each domain’s IP address, and Bind—which shows whether or not the given domain is bound to its IP address. This list can be sorted in ascending or descending order by any column. Simply click the column by which you wish to sort the list and it will be sorted by that column in ascending order. Click the same column again to sort it in descending order.


Domain name

Enter the domain name of the secondary domain that you wish to host.


IP address

Enter the IP address to associate with the domain being added or edited.


Bind to this IP

Click this checkbox if you want to bind the secondary domain to its IP address.


Add

Click this button to add the secondary domain along with its IP address and binding status to the Domain List.

To add a secondary domain to the Domain List:

1.	Enter the Domain Name and IP Address.

2.	Click Bind To This IP (only if you want to bind the domain to its IP address).

3.	Click Add.


Replace

When you click an entry in the Domain List, its settings will appear in the corresponding controls. Click this button after making any desired changes to the information to replace the entry with the new settings.

To edit a secondary domain:

1.	Click the Domain List entry that you wish to edit.

2.	Make any desired changes to the information the will appear in the controls.

3.	Click Replace.


Remove

After selecting an entry in the Domain List, click this button to remove it from the list.


Enable MDConfig remote configuration engine

Click this Checkbox to enable support for remote configuration. MDaemon will listen for connections on the MDConfig port specified on the Domain Configuration Editor (page 35). With this switch turned off, all attempts to remotely configure the server using MDConfig will fail. The MDConfig server can also be enabled/disabled from the Message Router.


Enable WebConfig remote configuration using port [XX]

Enable this checkbox if you want to enable MDaemon’s WebConfig server. With this server active, MDaemon’s files can be edited through the use of a web browser by connecting to MDaemon’s primary domain URL and specifying the port on which WebConfig is listening (page 35). For example: if your primary domain’s URL was “www.altn.com” and WebConfig was listening on port 8083, then you could reach WebConfig by pointing you browser to “http://www.altn.com:8083”. The WebConfig server can also be enabled or disabled from the Message Router.


Administrator

MDConfig must send this login and its accompanying password in order to gain administrator access to the remote configuration process. This level of access permits changes to every configuration aspect of MDaemon.


Password

This password must be provided along with the Administrator login in order to gain administrator access to remote configuration.


Supervisor

When this login with its accompanying password is sent by MDConfig, supervisor access to remote configuration will be granted. This level of access permits changes to accounts and account related functions within MDaemon such as auto-responders, account aliases, and account settings.


Password

This password must accompany the Supervisor login in order for the client to gain supervisor level access to remote configuration.


Only allow connections from these IP's

The IP addresses listed here are the only ones from which MDaemon will accept a remote configuration connection.  Wildcards are permitted.


New IP address

To add an IP address from which you wish to allow Remote Configuration, enter the IP address here and then click the Add button.


Add

Click this button to add an IP Address that you have entered into the New IP Address text box.


Remove

Click this button to remove a selected IP address from the display window.


MDConfig Backup Directory

If specified, MDaemon will backup original copies of updated configuration files to this directory.


Enable WorldClient server

Click this checkbox to enable the WorldClient server. You may also enable/disable WorldClient from the File menu or Statistics and Shortcuts frame of the Message Router.

Note
If you are using WorldClient Standard but have WorldClient Pro installed on the same machine, MDaemon will ask you if you want the controls on this dialog to apply to WorldClient Pro instead.


Run WorldClient server using this TCP port

This is the port on which WorldClient will listen for connections from your users’ web browsers.


Sessions not composing a message expire after XX inactive minutes

When a user is logged in to WorldClient but is not composing a message, this is the amount of time that their session may remain inactive before WorldClient will close it.


Sessions composing a message expire after XX inactive minutes

This timer governs how long a user’s session will be kept open while they are composing a message and the session remains inactive. It is a good idea to set this timer higher than the Sessions Not Composing a Message… timer since inactivity time is typically greater while a user is composing a message. This is because composing a message requires no communication with the server until the message is sent. Therefore, larger messages result in longer times of inactivity.


WorldClient pro only options

The controls in this section apply exclusively to WorldClient Pro. If you do not have WorldClient Pro, this section can be disregarded. Visit www.WorldClient.com for more information about WorldClient Pro.


Use WorldClient Pro if it is installed on this Computer

Click this option if you have WorldClient Pro installed on the same machine as MDaemon and you would want this dialog’s controls to apply to it instead.


Stop & start WorldClient Pro when MDaemon stops & starts

Click this checkbox if you want MDaemon and WorldClient to always run at the same time. Stopping or starting MDaemon will automatically do the same to WorldClient.


Automatically synchronize accounts between MDaemon and WC Pro

Enable this control if you want MDaemon and WorldClient accounts to be automatically synchronized. Whenever an account is created or edited in MDaemon, the same account will be created or edited in WorldClient Pro. The reverse is true as well.


Address Suppression POPUP
Address suppression

Use Setup|Security Settings|Address Suppression… to edit the addresses on the suppression list. This list contains addresses that are not allowed to send mail traffic through your server. If a message arrives from an address on this list, the message will be immediately deleted. This is useful for controlling problem users. Addresses may be suppressed on a per domain basis or globally (applied to all MDaemon domains).


Currently suppressed addresses

This window displays all currently suppressed addresses listed by the domain that is suppressing them.


Domain name

Choose the domain to which this suppressed address will apply. In other words, what domain do you want to prevent from receiving mail from the suppressed address? Choose “All Domains” from this list to suppress the address globally.


Email address

Enter the address that you wish to suppress. Wildcards are accepted, therefore “*@badmail.com” will suppress any message from any user at “badmail.com” and “frank@*” will suppress any message from anyone named “frank”, regardless of the domain the message is from.


Remove

Click this button to remove an entry that you have selected in the Currently Suppressed Addresses display.


Add

Click this button to add the designated user to the suppression list.


Refuse to accept mail during SMTP session

If selected, mail to the selected domain from a suppressed address will be refused during the SMTP transaction stage. When this condition is set for a particular domain, no mail to that domain from a suppressed address will ever be stored on your server, even in temporary work files. This feature is set on a per domain basis.


Inform sender when their mail is rejected

If selected, a polite message will be routed back to the suppressed sender telling him or her that their message was deleted. This feature is set on a per domain basis.

Note
In order for this function to work, a copy of the message must be downloaded during the SMTP session so that it can be parsed. Consequently, this option is incompatible with the “Refuse To Accept Mail During SMTP Session” switch.


IP Screening

Use the Setup|Security Settings|IP Screening… menu selection to configure IP Screening. The IP Screen is a list of IP addresses that you have designated as either acceptable or non-acceptable. How the server treats attempted connections from the IP addresses listed on the IP Screen depends on the security setting selected in the Screen editor. You may specify a list of IP addresses and then configure the server to only allow connections from those on the list, or you can configure it to abort any connection attempt from an IP address on the list. Wildcards are acceptable in any of the four IP address positions:

*.*.*.*	Matches to any IP address

206.*.*.* 	Matches to any IP that begins with 206

206.97.*.239	Matches to IP addresses from 206.97.0.239 to 206.97.255.239


Current IP screen settings

This window displays all IP addresses that are being screened by MDaemon. They are listed either globally or according to the Local IP Address to which they apply.


Local IP

Choose from the drop-down list either “All IP’s” or the local IP to which you wish to apply the screen.


Remote IP

Enter an IP address that you wish to add to the screened list.  You must enter this address in dotted decimal form. The IP Screen works with IP addresses only. Click the Add button to add the specified IP address to the address listing.


This remote IP can connect

Selecting this option will allow only those IP addresses specified under the given domain to connect and deliver messages. Attempts to connect via IP addresses not specified in the listing will be refused and immediately aborted. This option is useful for setting up private mail network systems.


This remote IP can not connect

Selecting this option will allow all IP addresses other than those specified in the address listing to connect and deliver messages.  Attempts to connect from IP addresses specified in the address listing will be refused and immediately aborted.  This option is useful for excluding IP’s that cause problems for your mail transport system.


Add

Click this button to add the address specified in the IP Address control to the Current IP Screen Settings window.


Remove

Click this button to remove a selected entry from the listing.


Undefined IP's can connect to this local IP

When this option is chosen, all IP addresses not listed in the IP Screen will be allowed to connect.


Undefined IP's can not connect to this local IP

When this option is chosen, only those IP addresses specifically granted permission in the IP Screen will be allowed to connect.


IP Shielding

Use the Setup|Security Settings|IP Shielding… menu selection to configure IP Shielding. The IP Shield is a list of domain names and matching IP addresses that will be checked during the SMTP MAIL FROM: command. An SMTP session claiming to be from someone at one of the listed domains will be honored only if it is coming from a machine with one of the associated IP addresses. For example, suppose your domain name is mdaemon.com and your local LAN computers use IP addresses in the range from 192.168.0.0 to 192.168.0.255. With this information you can setup the IP Shield to associate the domain name mdaemon.com with the IP address range 192.168.0.* (wildcards are allowed). Thus anytime a computer connects to your SMTP server and states, "MAIL FROM <someone@mdaemon.com>", the SMTP session will continue only if the connecting computer has an IP address within the required range from 192.168.0.0 to 192.168.0.255.


Ensure sender's address is valid if it claims to be from one of our domains

If the person sending a message claims to be from one of MDaemon’s domains, the account used will be verified against the account database. The local account must exist or MDaemon will refuse to accept the message for delivery.


Local sender must have checked POP mailbox within last [XX] minutes

With this feature enabled, whenever someone claims to be a local user they must have logged in and checked their local mailbox within the specified number of minutes before they will be allowed to send mail.


Messages collected via ATRN are exempt from this requirement

Click this control if you want messages collected via ATRN to be exempt from the POP Before SMTP requirement.


Authenticated sender are valid regardless of the IP they are using

When this control is active, currently shielded IP addresses will not apply to users that have been authenticated. Mail will be accepted from them regardless of the IP address from which they are connecting.


Authenticated users are exempt from the POP Before SMTP requirement

If you are utilizing the POP before SMTP security feature above, you may click this control to make authenticated users exempt from this restriction. An authenticated user will not need to perform a POP check before sending mail.


Global AUTH password

If the Authenticated senders are valid regardless of the IP they are using control is enabled, MDaemon accounts configured for dynamic NT authentication must use this global AUTH password for authentication instead of their normal NT password.


Currently Defined Domain/IP Pairs

This is the list of domain names and their corresponding IP addresses that will be compared when someone attempts to connect to MDaemon claiming to be from one of them.


Messages to valid local users are exempt from domain/IP matching

Click this option if you want only those messages that are destined for a non-local user or invalid local user to be checked for a domain/IP match. This will prevent others from posing as one of your local users in order to relay their mail through your server but save resources by not checking those sending messages to users on your server.


Domain name

Enter the domain name that you wish to associate with a specific IP address range.


IP address

Enter the IP address that you wish to associate with a domain name.  You must enter this address in dotted decimal form.


Add

Click the Add button to add the domain and IP address range to the listing.


Remove

Click this button to remove the selected entries from the listing.


AUTH/POP Before SMTP

As a security measure, many ISPs have begun to require their customers to perform a POP check or some other form of authentication before allowing them to send mail through the ISP’s mail server or dequeue the customer’s mail. The AUTH/POP Before SMTP feature makes it possible to fulfill this ISP requirement.


Perform a POP check before sending waiting mail

Click this checkbox if you are required to perform a POP check before sending waiting mail.


Host name or IP address

Enter the host or IP address to which you wish to connect.


POP logon

This is the POP account’s logon or account name.


POP password

This is the account’s POP password.


Use ESMTP AUTH when sending mail to ISP gateway

As an added security measure, some ISPs require their customers to log in using the ESMTP AUTH command before they are allowed to send mail through the ISPs servers. If your ISP requires you to do this then you can use the controls under this section to configure MDaemon to do so.


AUTH logon

Enter you AUTH logon here.


AUTH shared secret

This is the password used in the ESMTP AUTH command’s shared secret.


Use ESMTP AUTH when sending dequeue signal to host

Besides requiring their customers to authenticate themselves before sending mail, some ISPs require their customers to authenticate themselves before sending the signal to dequeue any incoming mail that is being held for them.


AUTH logon

If authentication is required before sending the signal to dequeue your mail, this field is where you will place the required AUTH logon parameter.


AUTH shared secret

Enter the password used in the AUTH shared secret required by you ISP.


Enable spam blocker engine

Click this checkbox to turn on Spam Blocker.


Spam blocker hosts

MDaemon will query each of these hosts when performing a Spam Blocker lookup on an IP address. If a host replies to the query with a positive result, MDaemon will refuse to accept the message from that IP address, and will also send the short message associated with the host that blacklisted the address.


New host

If you wish to add a new host to be queried for blacklisted IP addresses, enter it here.


Message

This is the message that will be sent when an IP address has been blacklisted by the New Host.


Remove

Select an entry from the Spam Blocker Hosts list and click this button to remove it from the list.


Add

After entering a New Host and Message, click this button to add it to the Spam Blocker Hosts list.


Exceptions

Click this button to open the Spam Blocker Exceptions dialog on which you can designate IP addresses that will be exempt from Spam Blocker lookups. You should always include your local IP address range to prevent lookups on it. 127.0.0.1 is already exempt and therefore doesn’t need to be added to the list.


Flag messages from blacklisted sites but go ahead and accept them

When this control is enabled, MDaemon will not refuse messages that receive a blacklisted result. However, those messages will have X-RBL-Warning: header inserted. You can then use the Content Filter feature to search for messages with this header and do with them as you please.


Check DomainPOP collected mail also

When this switch is enabled Spam Blocker will check the IP address stamped in the most recent "Received" header of downloaded messages.


Caching

Click this button to open the Spam Blocker Caching dialog used for caching recent Spam Blocker results.


Mail relaying

Use the Setup|Security Settings|Relay Control… menu selection to define how your server reacts to mail relaying.  When a message arrives at your mail server that is neither from nor to a local address, your server is being asked to relay (or deliver) the message on behalf of another user. If you do not want your server to relay mail for unknown users you can use the settings provided here.


This server does not relay mail for foreign domains

When this switch is selected, MDaemon will refuse to accept messages for delivery that are both FROM and TO a non-local user.


Refuse to accept mail for nonexistent local users

When this checkbox is enabled, MDaemon will refuse to accept mail that is for a local domain but addressed to a nonexistent user. “Local” includes both LAN and Gateway domains.


It's OK to relay mail for aliases that include foreign domains

Click this control if you want MDaemon to relay mail for Address Aliases regardless of your Relay Control settings.


Trusted domains

Domains that you list here are exceptions to the no-relay rule. These domains are “trusted” by your server and MDaemon will not refuse to relay mail for their users.


New trusted domain

Enter a new domain name to be added to the Trusted Domains list.


Add

Click this button to add the new domain to the Trusted Domains list.


Remove

Click this button to remove the selected entries from the Trusted Domains list.


Trusted IP addresses

IP addresses that you list here are exceptions to the no-relay rule.  These IP addresses are “trusted” by your server and MDaemon will not refuse to relay mail for their users.


New trusted IP address

Enter a new IP address to be added to the Trusted IP Addresses list.


Add

Click this button to add the new IP address to the Trusted IP Addresses list.


Remove

Click this button to remove the selected entries from the Trusted IP Addresses list.


Changing header text on the fly

The "Outbound Domain Conversion" feature has been replaced with the "Header Translation" feature.  This new dialog can change any portion of text found within a header to a new value, whenever a message is detected which must leave your domain and travel across the Internet. Your old "Outbound Domain Conversion" settings will be migrated to this new "Header Translation" feature.  It works like this: You specify the text you want to search for and its corresponding replacement value.  MDaemon will then search through all the headers in the message and make the replacements. You may also specify headers that MDaemon should not modify (such as "Subject:" or "Received:" headers) by clicking the "Exceptions" button on this dialog.

This feature is necessary for some MDaemon configurations in which the local domain name is fictitious or different from the domain name that must appear on outbound mail. In such a situation, Header Translation could be used to change every occurrence of "@localdomain.com" to "@RemoteDomain.com".

This feature is much more powerful and versatile than the old "Outbound Domain Conversion" feature while retaining the same basic functionality.


Existing header text

Type the text that you want to be replaced when it is found within the headers of any outbound message.


New header text

This text will be substituted for that which you specified in the Existing Header Text field.


Add

Click this button to add the above text parameters to the Current Header Translations list.


Translate headers in forwarded messages

Click this checkbox to cause the header translations to apply also to messages automatically forwarded from a local domain to a non-local domain.


Current header translations

This list contains the portions of text that MDaemon will scan for in the outbound message headers, and the text that will be substituted when a match is found.


Remove

Select an entry in the Current Header Translations list and then click this button to remove it from the list.


Exceptions

Click this button to open the Header Translation Exceptions dialog. This dialog is used for specifying any Headers that you wish to be omitted from the Header Translation process.


IP Cache

In order to speed message delivery and shorten mail processing time MDaemon caches the IP addresses of all hosts with which it comes in contact. These IP’s are stored and the cache is checked each time MDaemon requires a DNS resolution on a domain name. If the domain name needing resolution is found in the IP cache then the DNS lookup is skipped, which can save a surprising amount of processing time. The settings in this window allow you to manipulate the parameters under which the cache will operate. You may also manually add and remove entries and set the maximum size of the cache. The IP Cache can be reached from the Setup|IP Cache… menu selection.


Domain

Enter the domain name that you wish to add to the IP cache.


IP

Enter the IP address that you wish to add to the IP cache.


Max cached entries

This value determines how large the cache may be. Once this setting has been reached, the next cache entry will bump the first one out of the cache.


Default time to live

This is the default value in minutes that an entry in the IP Cache can survive. Once the entry has been in the IP Cache for this number of minutes, MDaemon will remove it.  If you want to set a permanent entry in the IP Cache then designate the Default Time To Live as 9999 in which case the entry will never expire.


Add

Once you have manually entered a domain name and IP address, click this button to add them to the cache.


Remove

Select an entry  in the Current Cached IP’s window and then click this button to remove it.


Clear cache at each processing interval

If selected, the entire contents of the cache will be flushed at the start of each mail session. This allows the cache to be refreshed at each processing interval.


Automatically cache uncached domains

This switch governs MDaemon’s internal auto-caching engine. If you want MDaemon to cache domains automatically then enable this option. If you want to build the IP Cache yourself, then clear this checkbox.


No cache

Click this button to bring up a list of domain names and/or IP addresses that you never want MDaemon to add to the IP Cache.


Clear

This button will flush the cache.


DNS lookup

The DNS Lookup utility (Setup|Perform a DNS Lookup…) can be very useful when used in conjunction with the IP Cache. DNS Lookup makes it possible for you to quickly and easily perform a DNS lookup for any valid Internet domain name. A successfully resolved domain name lookup will display the domain’s A-Record and any MX-Records that might be listed. There is also a control that can be used to automatically add the results of a successful lookup to the IP Cache.


Host information

Enter the domain name whose DNS information you wish to retrieve.


Add results to IP cache

Click this checkbox if you want the results of DNS lookups to be added to the IP Cache.


Domain name

This is the name of the resolved domain name.


Domain IP

This is the resolved domain’s IP address.


MX-record results

This window will display any MX records listed for the resolved domain.


Lookup!

Click this button to perform a DNS lookup for the domain name that you have listed in the Host Information section.


Send/Receive scheduler

Click the Setup|Send/Receive Scheduler… menu selection to open MDaemon’s Send/Receive Scheduler. This dialog makes it possible for you to schedule MDaemon’s Local, Remote, RAW, and System mail processing events as extensively or as simply as you prefer. You can schedule exact times for mail delivery and collection and/or use a counter to process mail at regular intervals. You can also set conditions that will trigger mail processing at unscheduled times such as when a certain number of messages are waiting to be delivered, or when a message has been waiting a specified amount of time.


Local/RAW/System mail processing interval

Slide this bar left or right to specify the time interval between mail processing sessions. It can be configured to count down from a range of 1 to 60 minutes, after which time MDaemon will Process Local, RAW, and System Mail before beginning the countdown again.  By default, this gauge only applies to Local, RAW, and System Mail. However, by checking the Deliver Remote Mail At This Inteval Also control it will apply to Remote Mail as well.  When this checkbox is cleared, Remote Mail processing intervals will be determined by the other scheduling controls on the Send/Receive Scheduler.


Deliver local mail immediately upon reception

When this option is selected, any Local, RAW, or System Mail will be processed and delivered each time an incoming SMTP session has completed.  This has the effect of instantaneous delivery of local messages.


Deliver remote mail at this interval also

If this checkbox is selected, the slide bar instead of the Scheduler will determine when Remote Mail is sent and/or collected. The rest of the controls in the Scheduler will be “dimmed” and will no longer apply to Remote Mail processing.


Simple scheduling

There are numerous ways a remote mail session can be triggered in MDaemon. Several of them will be discussed here.  The Simple Scheduling feature is handy when you wish to setup a remote mail processing interval that should occur at a regular time interval after the last one regardless of the trigger that initiates the session. Unlike the rigidly fixed intervals used when setting up specific times or using the slide bar, this feature’s time interval will reset whenever mail is processed regardless of what caused the mail session to be initiated.

Note
In order for Simple Scheduling to take effect for a given day at least one timed entry must exist for that day in the Scheduled Times list. For example, suppose you wanted to schedule 45 minutes between dialup sessions but only on Monday through Friday. You would need to enable the Simple Scheduling option and enter 45 minutes into the control and then enter at least one scheduled time for each day (Monday, Tuesday, Wednesday, Thursday, and Friday). Since there would be no scheduled time for Saturday or Sunday, those days would be exempt and would not trigger a Remote Mail session. The hour and minute setting you designate when you setup your trigger days doesn’t matter; Simple Scheduling only checks whether there is an entry present for that day.


Always send Mail if there's XX or more messages waiting in the outbound queue

MDaemon will trigger a mail session whenever the number of messages waiting in the outbound queue meets or exceeds the number that you specify here. These sessions are in addition to any other normally scheduled sessions.


Always send mail if a waiting message is more than XX minutes old

When this control is enabled, MDaemon will trigger a mail session whenever a message has been waiting in the outbound queue for the number of minutes specified. These sessions are in addition to any other normally scheduled sessions.


What day?

Select the days that you wish to schedule.


What hour?

Select the hour that you wish to schedule.


What minute?

Select the minute that you wish to schedule.


Add

Once you’ve selected the day, hour, and minute click this button to add this time to the list of scheduled events.


Remove

Clicking this button will remove an entry that you have selected from the schedule listing.


Clear all

This button removes all entries from the schedule listing.


RAS setup

This button is provided so that you can quickly review or edit your RAS settings.

TIP
The amount of time needed to load the Scheduler when MDaemon starts will vary.  The length of time this process will take is proportional to the number of event entries that have been created. Most configurations will do well to simply use the slide bar and Simple Scheduling to control mail processing intervals. For example, it is wasteful to schedule every minute of every day using the scheduler when you can simply set the slide bar to one minute intervals, place it in control, and accomplish the same thing. On the other hand, if you want the remote intervals to be further apart than the local intervals, but still frequent, then you could use Simple Scheduling for Remote and the slide bar for Local.

See:

RAS Dialup Settings


Enable RAS dialup/dialdown engine

Selecting this option will cause MDaemon to use the settings specified here to make a connection to a remote host before sending and/or receiving remote mail.


Dialup only if remote mail is waiting in outbound queue

When this switch is checked, MDaemon will not dial up the ISP unless there is remote mail waiting in the Remote queue. This may be beneficial in some circumstances but be aware that if MDaemon does not dial up then it cannot do any mail collecting either (unless it is delivered across the local LAN).


Notify [address] when dialup attempts fail

When selected, MDaemon will send a message to the specified address when a dialup event fails because of some error.


Make this many attempts to establish a session

MDaemon will attempt to connect to the remote host this many times before giving up.


After dialing, wait this many seconds for a valid connection

This value determines how long MDaemon will wait for the remote computer to answer and complete the RAS connection.


Once established, MDaemon will not close the RAS session

By default, MDaemon will shut down a created connection immediately after all mail transactions have been completed, and the session is no longer in use. Selecting this option will cause the connection to remain open even after all transactions have been completed.

Note
MDaemon will never close a connection that it did not create.


Keep sessions alive for at least XX  minutes

If enabled, this option will cause an MDaemon created RAS session to remain open for at least the number of minutes specified or until all mail transactions have been completed, whichever is greater.


Logon name

The value specified here will be passed to the remote host during the authentication process.


Logon Password

The value specified here will be passed to the remote host during the authentication process.


Use this RAS dialup profile

This drop-down list box allows you to select a session profile that has been previously defined through windows Dialup Networking or Remote Access Services Setup.


New profile

Click this button to create a new Dialup Networking or Remote Access Services profile.


Edit profile

Click this button to edit the currently selected Dialup Networking or Remote Access Services profile.


Maximize use of this connection profile

This switch causes MDaemon to monitor your connections so that if it detects that another program has established a connection it will process remote mail immediately regardless of scheduled times. If the connection remains open it will continue to process remote mail at regular time intervals based on the Use existing connection every XX minutes setting.


Hang-up now

This button will close the connection to the ISP. This button is active only if MDaemon has initiated the RAS session.


Use any currently active dialup session

Click this checkbox if you want MDaemon to be able to utilize other connection profiles when it detects that one is active. Whenever it is time to dialup, MDaemon will first check to see if there is an active connection that it can use rather than dialing.


Once connected, run this process

If a program is specified here, MDaemon will spawn a thread and execute the process. This is extremely useful for those who require Finger or some other program to unlock the ISP’s mailbox.


Pause Server For XX Seconds (-1 = infinite, 0=no waiting)

If the Once Connected, Run This Process control contains a valid entry then the server will pause its operations for the number of minutes specified here while it waits for the executing process to return. Entering “-1” will cause the server to wait indefinitely for the process to return.


Force process to shutdown after pause interval has elapsed

Sometimes the program you need to run may not exit once it has run its course; some programs require user intervention in order to close them down. This is not acceptable when the software must run unattended. If this switch is selected MDaemon will force the process thread to terminate once the number of seconds specified in Pause Server For XX Seconds has elapsed. This function does not work when the server is configured to wait indefinitely for the process to return.


These domains are on my local LAN

The domains listed here are considered by MDaemon to be part of your local LAN. Therefore, no dialup is required in order to deliver a message to one of them.


New local LAN domain

Enter a domain name to add to the Local LAN list and click the Add button to add it.


Relay mail for these domains

If this switch is selected MDaemon will relay mail for these domains. This provides some measure of control over the traffic sent to and from these domains.


Add

Click this button to add an entry to the list of LAN domains.


Remove

Click this button to remove a selected entry from the list of LAN Domains.


LAN domains

The domains listed here do not require DUN or RAS in order to be contacted. A message in the queue destined for one of these domains will not initiate a dialup session and will be spooled at scheduled local mail processing intervals. These .MSG files are stored in a directory called LNDOMAIN, which stems off the LOCALQ directory.


Enable DomainPOP mail collection engine

If selected, MDaemon will use the setting provided on this screen to collect mail from a DomainPOP mail host for local redistribution.


Host name or IP

Enter your DomainPOP host’s domain name or IP address here.


Logon name

Enter your login of the POP account used by DomainPOP.


Password or APOP shared secret

Enter the POP account’s password or APOP shared secret here.


Use APOP

Click this box if you wish to use the APOP command and CRAM-MD5 authentication when retrieving your mail. This makes it possible to authenticate yourself without having to send clear text passwords.


Leave a copy of message on host server

If selected, MDaemon will not remove collected messages from your DomainPOP mail host.


Delete messages once [XX] or more have accumulated (0 = no limit)

If you are leaving messages on your ISP server then they will be deleted once this number is reached.  Enter "0" if you want messages to remain on the server regardless of the number.

Note
Some ISP’s may limit the amount that you are allowed to store in your mailbox.


Don't download messages larger than [XX] KB (0 = no limit)

Messages greater than or equal to this size will not be downloaded from your DomainPOP mail host.  Enter "0" if you want MDaemon to download messages no matter the size.


Delete large messages from DomainPOP and MultiPOP hosts

Click this switch and MDaemon will delete messages that exceed your maximum set size.  The messages will simply be removed from the DomainPOP and MultiPOP mail hosts and will not be downloaded.


Warn postmaster about large DomainPOP messages

Click this switch and MDaemon will send a warning to the postmaster whenever a large message is discovered in the DomainPOP mailbox.


Download messages according to size (small messages first)

Enable this checkbox if you want the message downloading order to be based on size—beginning with the smallest and proceeding to the largest.

Note
This option retrieves smaller messages quicker but requires a larger amount of internal sorting and processing.


Warn account holder and delete over quota message

When this option is chosen and a message is collected for an account that is over its quota (designated on the Quotas tab of the account editor), MDaemon will delete the message and send a warning to the user letting them know that their account is over its limit.


Warn account holder and forward over quota message to Postmaster

When this option is chosen and a message is collected for an account that is over its quota (designated on the Quotas tab of the account editor), MDaemon will forward the message to the Postmaster and send a warning to the user letting them know that their account is over its limit.


DeDupe Collected Mail Using The Message-ID Field

If this option is selected MDaemon will remember the value of the specified header and will not process additional messages collected in the same processing cycle which contain an identical value. The Message-ID field is the natural header to use but the actual header can be anything you want.


Parse 'Received' headers for email addresses

This switch makes use of a powerful yet seldom used optional RFC-822 regulation. It is possible to store the recipient information ordinarily found only within the message’s envelope in a message header so that parsers of the mail message will be able to glean the actual recipient address by merely inspecting the headers later. MDaemon will attempt to capitalize on this optional rule if you have this switch set by parsing ALL the “received” headers found within the mail message for valid addresses.


Skip over the first xx "received" headers

Sometimes it is useful to process Received headers but starting at the nth occurrence of them.  This setting allows you to enter the number of “Received” headers that MD will skip over before beginning its processing.


Stop parsing if "received" yields a valid local address

If while parsing a “received” header MDaemon detects a valid local address, this switch will cause all further parsing to stop and MDaemon will not search the message for more potential delivery addresses.


Parse "Subject:" header for address inside "(" and ")" characters

When this is selected and MDaemon finds an address contained in “( )” in the “Subject:” header of a message, this address will be added to the message’s list of recipients along with any other parsed addresses.


Parse these headers for email addresses

This control lists the headers that MDaemon will parse in an attempt to extract addresses.  Every header listed here is checked for addresses.


New header

Enter the header you wish to add to the header list.


Add

Add the header listed in the New Header control to the list.


Default

This button will clear the current contents of the header list and add MDaemon’s default list of headers. The default headers are typically sufficient to extract all addresses from the message.


Remove

This button will remove the selected entries from the header list.


Enable domain name replacement engine

This option is an attempt to cut down on the number of domain aliases your site will require.  When a message is downloaded *all* domain names in *all* addresses which are parsed from that message are instantly transformed into the one specified here.


Ignore unknown local addresses parsed from messages

As mentioned above, the Domain Name Replacement feature will alter the domain name in all email addresses parsed from the message, converting it into the one you specify on this screen.  This could create some addresses which do not have a corresponding mailbox account at your site.  Since the domain name will match your primary domain name, MDaemon will consider such addresses local but undefined.  Such mail typically generates a “No Such User” message directed at the postmaster.  This switch will prevent the Domain Name Replacement Engine from generating “No Such User” messages.


Always strip the following text from all parsed addresses

Some ISP’s will stamp each message with a line that indicates who the recipient of the message should be along with a bit of routing information appended to the address on either the left or right hand side.  This stamp would be perfect to use for parsing the recipient address except that the additional routing information makes this impossible without a lot of account aliasing.  Rather than do all that you can simply specify the value of this appended text in the edit control associated with this feature and MDaemon will strip any occurrence of this text from all addresses that it parses.


Existing rules

This list shows you the rules that you have created and will be applied to your messages.


Remove

Press this button and the selected rules in the Existing Rules list will be removed.


Default

Press this button to remove all existing rules and replace them with a predefined set of defaults.


Clear all

This button removes all existing rules.


If the parsed address

Is equal to, is not equal to, contains, does not contain

This is the type of comparison that will be made when an address is compared to this routing rule. MDaemon will search each address for the text contained in the "This text" field and then proceed based upon this control’s setting—does the address’s complete text match exactly, not match exactly, contain the text, or not contain it at all?


This text

Enter the text that you want MDaemon to search for when scanning the addresses.


Then do this with the message

This control lists the available actions that can be performed if the result of the rule is true.  Here is a list of actions and what they do:

Don’t deliver to this address - Selecting this rule will prevent the message from being delivered to the specified address.

Send to user or group of users - Selecting this action will bring up a dialog that will allow you to create a list of email addresses that should receive a copy of the message being processed.


Forward summary of non-local addresses to postmaster

If this option is selected MDaemon will send a single copy of the message to the postmaster along with a summary of the non-local addresses that the parsing engine extracted using the current set of headers and parsing rules.


Deliver non-local mail to all remote recipients

If this option is selected MDaemon will deliver a copy of the message to any non-local recipient that it finds within the inspected headers.


Do not deliver mail addressed to non-local addresses

If this option is selected MDaemon will remove from the recipient list any address that is non-local. It will be as if MDaemon never parsed remote addresses from the original downloaded message.

Note
The various Unless.. buttons allow you to define addresses which are exceptions to the rules.


Place an extra copy of all downloaded mail into this directory

This is a safety feature to ensure that you don’t lose any mail due to unforeseen parsing or other errors that might occur when downloading mail in bulk quantities.


Activate real name matching engine

This feature allows MDaemon to determine who should receive a DomainPOP collected message based not upon what the email address is but upon what the text portion (typically a person’s real name) is.  For example, a message’s TO header might read:

TO: “Joe User” <common-mailbox@isp.com>

or

TO: Joe User <common-mailbox@isp.com>

Name Matching does not care about the “common-mailbox@isp.com” portion of the address.  It instead extracts the “Joe User” portion and attempts to lookup this name in the MDaemon user database.  If a match is found to an account’s real name field then that account’s local email address is used for delivery purposes.  If no match is made then MDaemon reverts to delivering the message to the email address parsed from the data (common-mailbox@isp.com in this example).

Note
The real name portion of the address should not contain a comma, semi-colon, or colon character so take care when you setup this information in your mail clients.

The Name Matching feature is only active in conjunction with the DomainPOP Mail Collection engine. If you wish to use this feature, you must make sure that you have DomainPOP enabled. DomainPOP can be reached from the Setup|DomainPOP Mail Collection menu selection.


Only apply this feature if the address portion matches this value

This control allows you to specify an email address that must be present in the extracted data in order for the real name matching process to proceed.  This allows you a measure of control over when the Name Matching feature will be employed.  For example, you can specify an address such as “common-mailbox@isp.com” and then only addresses matching this value will be candidates for Name Matching.

Suppose you have “common-mailbox@isp.com” in this control.

This means that:

TO: “Joe User” <common-mailbox@isp.com> will be a candidate for Name Matching while TO: “Joe User” <Joe@mdaemon.com> will not.


Enable content filtering engine

Click this checkbox to enable content filtering. All messages processed by MDaemon will be filtered through the content filter rules before being delivered.


Scan no more than [xx] KB of the message

Enter the maximum number of Kilobytes that you want the content filtering system to scan in each message for comparing to the filter rules. Scanning will start at the top of the message and proceed until this amount is reached, then MDaemon will move to the next message. Setting this value to "0" will cause the entire message to be scanned regardless of the size.


Existing content filtering rules

This box lists all rules in the order that they will be applied to a message. This makes it possible for you to arrange your rules to achieve a greater level of versatility.

For example: If you have a rule that deletes all messages containing the words, "This is Spam!" and a similar rule that sends those messages to the Postmaster, then putting them in the right order will enable both rules to be applied to the message. This assumes that there isn’t a "Stop Processing Rules" rule that applies to the message higher up in the list. If so, then you would use the Move Up/Move Down buttons to move the "Stop" rule below the other two. Now any message containing "This is Spam!" would be copied to the Postmaster and then deleted.

Note
New to MDaemon Version 3 is the capability to create rules that will perform multiple tasks and use and/or logic. Therefore, considering the example above, you can now create a single rule that will accomplish all of those tasks and more.


New rule

Click this button to create a new content filter rule. This will open the Setup New Rule dialog.


Edit rule

Click this button to open the selected rule in the Modify Rule editor.


Copy rule

Click this button to clone the selected content filter rule. An identical rule will be created and added to the list. The new rule will be given a default name called "Copy of [Original Rule Name]". This is useful if you wish to create multiple similar rules. You can create a single rule, clone it several times, and then modify the copies as needed.


Delete rule

Click this button to delete the selected content filter rule. You will be asked to confirm your decision to delete the Rule before MDaemon will do so.


Move up

Click this button to move the selected rule up.


Move down

Click this button to move the selected rule down.


Rule description [rule name] (enabled/disabled)

This box displays the currently selected rule in its internal script format. Click any of the rule’s conditions (listed as a hyperlink) and the appropriate editor will be opened for changing that particular condition.


Create rule

This dialog is used for creating Content Filter Rules. It is reached by clicking the New Rule button on the Content Filter dialog.


Give this rule a name

Type a descriptive name for your new rule here. By default it will be called "New Rule #n".


Select conditions For This Rule

This box lists the conditions that may be applied to your new rule. Click the checkbox corresponding to any condition that you want to be applied to the new rule. Each enabled condition will appear in the Rule Description box below. Most Conditions will require additional information that you will specify by clicking on the Condition’s hyperlink in the Rule Description box.

If the [HEADER] contains—Click any of these options to base your rule on the content of those particular message headers. You must specify the text for which to scan.

If the user defined [# HEADER] contains—Click one or more of these options to base the rule on message headers that you will define. You must specify the new header, and the text for which to scan.

If the MESSAGE BODY contains—This option makes the contents of the message body one of the conditions. This condition requires you to specify a text string for which to search.

If the MESSAGE has Attachment(s)—When this option is selected, the rule will be contingent upon the presence of one or more message attachments. No additional information is required.

If the MESSAGE SIZE is greater than—Click this option if you want the rule to be based upon the size of the message. The size must be specified in KB. Default is 10KB.

If the MESSAGE HAS A FILE called—This option will scan for a file attachment with a particular name. The filename must be specified.

If the MESSAGE IS DIGITALLY SIGNED—The condition applies to messages that have been digitally signed. No further information is required by this condition.

If ALL MESSAGES—Click this option if you want the rule to be applied to all messages. No further information is required; this rule will affect every message except those to which a "Stop Processing Rules" or "Delete Message" action has been applied in a previous rule.


Select actions for this rule

MDaemon can perform these actions if a message matches the rule’s conditions. A few Actions will require additional information that you will specify by clicking on the Action’s hyperlink in the Rule Description box.

Delete Message—Selecting this action will cause the message to be deleted.

Strip All Attachments From Message—This action causes all attachments to be stripped from the message.

Move Message To Bad Message Directory—Click this action to cause a message to be moved to the bad message directory.

Skip n Rules—Selecting this action will cause a specified number of rules to be skipped. This is useful in situations where you may want a rule to be applied in certain circumstances but not in others.

For example: you may wish to delete messages that contain the word "Spam", but not those that contain "Good Spam". To accomplish this you could create a rule that deletes messages containing "Spam" and then place above it another rule that states "if the message contains "Good Spam" then Skip 1 Rule".

Stop Processing Rules—This action will skip all remaining rules.

Copy Message To Specified User(s)—Causes a copy of the message to be sent to one or more recipients. You must specify which recipients are to receive the message.

Append Standard Disclaimer—This action makes it possible for you to create a small amount of text that will be appended as a footer to the message. Alternatively, it can add the contents of a text file.

For example: you could use this rule to include a statement that says "This email originated from my company, please direct any complaints or questions to me@mycompany.com".

Add Extra Header Item To Message—This action will add an additional header to the message. You must specify the name of the new header and its value.

Delete A Header Item From Message—This action will remove a header from a message. You must specify the header that you wish to delete.

Send Note To... —This action will send an email to a particular address. You will be able to specify the recipient, sender, subject, and a small amount of text. You can also configure this action to attach the original message to the note.

For example: you might wish to create a rule that will move all messages containing "This is Spam!" to the bad message directory and create another rule that will send a note to someone letting them know that this has been done.

Remove Digital Signature—Click this action to cause a digital signature to be removed from the message.

Run Process…—This action can be used to run a particular program when a message meets the rule’s conditions. You must specify the path to the program that you wish to run. You can use the $MESSAGEFILENAME$ macro to pass the name of the message to the process, and you can specify whether or not MDaemon should suspend its operations temporarily or indefinitely while it waits for the process to terminate. Further, you can force the process to terminate and/or run it in a hidden window.

Send Message Through SMS Gateway Server…— Click this option to send the message through an SMS Gateway Server. You must supply the Host or IP Address and the SMS phone number.

Copy Message to Folder…—Use this option to place a copy of the message into a specific folder.


Rule description

This box displays the new rule’s internal script format. Click any of the rule’s conditions or actions (listed as hyperlinks) and the appropriate editor will be opened for specifying any needed information.


Priority Mail

The Setup|Priority Mail… menu selection opens the Priority Mail dialog, which is used to define what constitutes Priority Mail on your system. Priority mail is delivered immediately by MDaemon regardless of scheduled mail processing intervals. When a new message arrives, MDaemon inspects its headers for a set of header/value combinations that you have specified on this dialog. If it finds them, it considers the message a high priority item and attempts to deliver it immediately.


Enable priority mail checking engine

Click this switch to enable the Priority Mail feature. MDaemon will inspect incoming messages for priority status.


Header

Enter the message header in this field. Do not include the ending colon character.


Value

Enter the value that must be found in the specified header in order for the message to be considered high priority.


Trigger even if value is a sub-string

When entering a new Priority Mail setting you may select this feature to enable priority matching of a portion (or sub-string) of a header value. For example, you could create a Priority Mail Setting for the “To” header with the value “Boss”. Then, any email containing “Boss@anything” in that header would be considered Priority Mail. If an entry is created without this feature enabled then the value of the header must match the entry exactly; matching only a portion will not be sufficient.


Remove

Click this button to remove a selected entry from the Current Priority Mail Settings window.


Add

After entering the Header/Value information in the specified text boxes, and after specifying whether this entry will apply to sub-strings, click the Add button to create the new Priority Mail entry.


Current priority mail settings

This window lists all the currently defined priority mail header/value combinations.  Double click on an item in this list to remove it.


Exceptions

This allows you to define field/value combinations that will cause a message to be considered an exception to the priority mail settings. This gives you more flexible control over this feature.


Log file

Click the Setup|Log File… menu selection to configure your Log File settings.  The log file is a useful tool for diagnosing problems and seeing what the server has been doing while unattended.


Log each day in its own file

If this option is selected then a separate log will be generated each day.  The name of the file will be "MD[YYYYMMDD].LOG".


Log each day by day of week

If this option is selected, a separate log will be generated for each day of the week. The name of the log files will be DAYOFWEEK.LOG (e.g. Monday.log, Tuesday.log, and so on).


Log everything in one file

Enable this switch to log all entries in a single file.


File name

If you elect to use the Log Everything In One File option then specify the name of the log file here. The log file will be stored in the Logs directory.


Max log file size [XX] KB

This is the maximum size in kilobytes that a log file may reach. Once this size is reached, the log file is copied to LOGFILENAME.OLD and a new log is started.


Perform no more than one automatic backup per day

When limiting the log file size, click this checkbox if you want no more than one log file to be backed up per day. Each day, the first time that the maximum log file size if reached it will be renamed to "*.OLD" and saved normally. The subsequent log file will continue to grow regardless of the maximum size specified. It will not be rolled over until the next day—even if the maximum size setting is surpassed.


Log detailed mail sessions

A complete transcript of each mail transaction session will be copied to the log file when this option is active.


Log summarized mail sessions

The option causes a summarized transcript of each mail transaction session to be copied to the log file.


Track sessions in real time

Ordinarily, session information is logged after the session is completed in order to conserve resources. Click this option if you want session information to be logged as in occurs.


Include parsing activities

There is a lot of message file parsing that MDaemon must periodically perform. Enable this switch if you want this information to be included in the log file.


Include RAS transcripts

Select this switch if you want MDaemon to copy RAS dialup/dialdown activities into the log file. This information is useful for diagnosing dialup problems.


Include POP TOP processing

Select this switch if you want MDaemon to copy POP TOP information into the log file.


Run MDaemon as a Windows NT system service

Enables the MDaemon service feature.


Service name

This is the name that NT will use for the service.


Start service

This is the initial state of the service.


Dependencies

A list of Services that must be active before the MDaemon service should attempt to load.


Force "date" header in all messages

When a message is encountered which doesn’t have a "Date:" header, MDaemon will create one and add it to the message file if this switch is selected. It will be the date on which MDaemon first receives the message, not when it was created by a mail client.  There are some mail clients that do not create this header, and since some mail servers refuse to honor such messages this feature will enable them to be delivered.


Force "Reply-To" header in all messages

When a message is encountered which doesn’t have a "Reply-To" header, MDaemon will create and add one to the message file using the address found in the "From" header.  If a "Reply-To" header is present but empty, MDaemon will create the header like this: Reply-To: "". This fixes problems for some mail clients.


Force "Message-ID" header in all messages

When a message is encountered which doesn’t have a "Message-ID" header, MDaemon will create one at random and insert it into the message.


Strip X-Type headers from local messages

MDaemon uses many server specific headers called X-Type headers in order to route mail and perform various MDaemon specific functions.  This switch will force MD to clean up after itself and remove these headers from messages as they are moved into local mailboxes.


Fix MS internet mail build 1160+ bug

This switch has been added in an attempt to deal with the Microsoft Internet Mail problem of messages not appearing on the display after they are downloaded.  With this switch turned on, MDaemon will strip consecutive CRLFCRLF sequences from the end of the message body.  Three sets of CRLF pairs at the tail end of a message file is the cause of the Microsoft problem.


Fix MS Outlook missing "From" field bug

Recent versions of Microsoft Outlook fail to create a FROM header when you compose a message.  The FROM field information is instead placed in the SENDER field.  This can confuse downstream mail servers as well as the recipient of your message!  Select this switch and MDaemon will create the missing FROM field using the address found in the SENDER field.


SMTP system uses ESMTP whenever possible

Select this switch if you wish to enable support for extended SMTP commands.


Use strict quotas (count subdirectories and hidden files)

When this box is checked, all files and subdirectories will apply toward any size or message number limitations placed on a user’s account mailbox. Otherwise, only actual message files will count toward these limitations.


Authenticate list posters using FROM: header

Usually senders to private lists are checked using the MAIL FROM value passed during the SMTP session. If you would rather have your system use the message’s FROM: header then enable this switch.


Enable disk checking for waiting message counts

This switch governs whether MDaemon will check the disk to count waiting messages in the mail queues.  Doing so can cause excessive disk spin over the long term.


Use small display font on router & session windows

Enables the small display font on the Router and Session windows.


Honor requests for account information

Provides the user list when requested via EXPN or LISTS commands.


Honor "Return-Receipt-To" headers

This switch determines how MDaemon will behave when faced with a request for deliver confirmation from an incoming message.  If set, a confirmation message will be dispatched to the sender of the triggering message.  Otherwise such requests are ignored.


Process/check for mail when server is first loaded

If selected MDaemon will create a mail processing event when it first loads.


Hide local IPs when processing message headers

Click this option to prevent MDaemon from placing local IP addresses into message headers when it processes mail.


Suppress confirmations when closing dialogs (expert mode)

Suppresses the ‘Are you Sure’ boxes when closing dialogs.  The only one that is not disabled is the one on program exit.


POP/IMAP/WorldClient Passwords are Case Sensitive

POP, IMAP, and WorldClient passwords will be case-sensitive when this control is checked.


Do not send Welcome message to new accounts

By default, MDaemon will generate a Welcome message based upon the welcome.dat file and distribute it to new users when their account is created. Enable this control if you want to prevent the message from being generated.


Use safe UIDL hash method

When you have configured MDaemon to leave messages on the host server after it has downloaded them, a UIDL hash method is used to identify those already retrieved messages. Previously MDaemon’s UIDL hash method was not compatible with Windows’ treatment of Daylight Savings Time. All stored messages would appear to be new and thus downloaded again a single time. Enable this feature if you want to switch to the new "safe" UIDL hash method that is unaffected by Daylight Savings Time.

Note:
Switching to the new hash method will cause all stored messages to appear to be new a single time and thus downloaded again. Thereafter messages will be unaffected by Daylight Savings Time.


Honor ESMTP VRFY commands

Click this switch to allow ESMTP VRFY commands.


Clear message counts at startup

When this checkbox is enabled, the message statistics information displayed on the main router window will be reset whenever MDaemon is launched.


Minimize to task bar in addition to system tray

Clear this checkbox if you do not want MDaemon to appear on the Windows taskbar when the program is minimized; only the tray icon will be visible. When this control is enabled and MDaemon is minimized it will appear on both the taskbar and in the system tray.


Remember states of SMTP/POP/IMAP servers across server reboots

If this control is enabled, MDaemon will ensure that the state of its servers (enabled or disabled) remains the same after a reboot.


Allow for SUN OS compatibility

Allow LF.LF for end of message mark in addition to the normal CRLF.CRLF sequence.


Auto responders are triggered by local as well as remote mail traffic

Sometimes it is advantageous to disable the auto-response engine for local mail traffic.


POP DELE command immediately removes messages from mailbox

Click this switch and MDaemon will delete immediately messages that a user has retrieved even if the POP session does not complete properly.


POP/IMAP servers honor APOP/CRAM-MD5 authentication methods

Enable this control if you want MDaemon’s POP and IMAP servers to honor the APOP and CRAM-MD5 methods of authentication. These methods provide extra security by making it possible for users to be authenticated without sending clear text passwords.


Apply content filter rules to list mail before individual messages for list members are cracked

When the MDaemon will crack list mail option is chosen on the Routing tab of the mailing list editor, enabling this control will cause the content filter rules to be applied to list messages before they are cracked and distributed to list members.


Don't accept SMTP delivered messages larger than XX KB.

Setting a value here will prevent MDaemon from accepting or processing SMTP delivered mail which exceeds a certain fixed size.  When this feature is active MDaemon will attempt to use the ESMTP SIZE command specified in RFC-1870.  If the sending agent supports this SMTP extension then MDaemon will determine the message size prior to its actual delivery and will refuse the message instantly.  If the sending agent does not support this SMTP extension then MDaemon will have to begin acceptance of the message, track its size periodically during transfer, and finally refuse to deliver the message once the transaction has completed.


Kill the socket connection if transmission of data exceeds XX KB

If the transmission of data during an MDaemon connection exceeds this threshold, MDaemon will close the connection.


In the system tray

Choose this option if you want MDaemon’s interface to be minimized at startup.


In a maximized window

Choose this option if you want MDaemon’s interface to be maximized at startup.


In a default window

Choose this option if you want MDaemon’s interface to appear in a default window at startup.


In a minimized window

If this option is selected MDaemon will create new mail session windows in a minimized state.


In a hidden window

If this options is selected MDaemon will create new mail session windows that are completely hidden from view.


In a default window

If this option is selected MDaemon will create new mail session windows using the default settings provided by Windows which relate to size and visibility.


Low disk space settings

Click this button to open the Disk Space Monitoring dialog.  This will allow you to set parameters on how MDaemon will react to low disk space situations.


Restrict MDStats GUI to a single instance only

Click this checkbox if you do not want more the one copy of MDaemon’s queue and statistics manager to be able to run at once. Attempting to launch MDStats when it is already running will simply cause the currently running instance to become the active window.


MDStats shows queue and mail directory subfolders

Click this checkbox if you want the queue statistics manager to display subfolders contained in the various queues and user mail directories.


Max number of accounts shown in GUI controls (0=show all)

This is the maximum number of accounts that will be shown in the drop-down list boxes on various dialogs. Further, when the value in this control is set to anything other than "0" (show all) the "Edit Account" and "Delete Account" options will no longer appear on the Accounts menu. Those functions will only be available from the Accounts Manager. You must restart MDaemon before any changes to this control will go into effect.


Max domains listed in tool window controls (0=show all)

This is the maximum number of secondary domains that will be listed under the "Servers" controls in the main display’s tool window. After changing this value, you must press F5 or restart MDaemon before the change will be visible in the tool window. This control cannot be set to anything less than 50.


Max number of log lines displayed before router window refresh

This is the maximum number of lines that will be displayed in the log window of the main display. When this number of lines is reached the window will be cleared. This has no affect on the log file. Only the display will be cleared.


Max number of log lines displayed before session windows refresh

This is the maximum number of lines that will appear in each session Connection window before it is cleared. This has no affect on the log file.


Honor ESMTP EXPN commands.

Click this checkbox if you want MDaemon to honor ESMTP EXPN commands.


SMTP server refuses mail which uses a NULL return path (RFC no-no)

Click this checkbox if you want the SMTP server to refuse mail that uses a NULL return path.


Hide ESMTP SIZE command parameter

Click this checkbox if you want the ESMTP SIZE command parameter to be hidden.


Return gateway mail to gateway dir after failed ETRN delivery attempt

Click this checkbox if you want MDaemon to return a gateway domain’s email to the gateway’s directory if it fails to be delivered during an ETRN delivery attempt.


SMTP sends 552 response to over quota condition (normally 452)

Enabling this control will cause a 552 response ("Requested mail action aborted: exceeded storage allocation") when delivery is attempted to a recipient whose account exceeds its quota. Normally there would be a 452 response ("Requested action not taken: insufficient system storage").


POP/IMAP servers always accept connections from IP [IP address]

The POP and IMAP servers will always accept connections from the IP Address entered into this field regardless of screening and shielding settings.


RAW server converts this many messages per interval

Use this control if you wish to limit the number of RAW messages that may be converted during any given mail processing interval. If the limit is reached then MDaemon will wait until the next processing interval before converting further messages.


Allow this many RCPT commands per message (RFC says 100)

Use this control if you wish to limit the number of RCPT commands that can be sent per message.


Add "Precedence: bulk" header to system generated mail

Click this option if you want all system generated messages (welcome messages, warnings, "could not deliver" messages, and so on) to have a "Precedence: bulk" header inserted.


Add this header and value to every list message [header]

If you wish to add a static header/value combination (such as "Precedence: bulk") to all list messages, then specify it here.


Pre-process mailing list mail

When a message arrives for a mailing list that should have been directed to the system address, MDaemon will reject it when this control is enabled. For example, a user may join or leave a list by placing the Subscribe or Unsubscribe command at the beginning of an email message and sending it to the system address. Oftentimes users erroneously try to send these messages to the list itself. Enabling this control will prevent these messages from being posted to the list.


Move account mail to new directories when domain names change

If this checkbox is enabled when you rename a domain, that domain’s existing account mail will be moved to directories with the new name. Otherwise, MDaemon will continue to use the old mail directory names.


MDaemon system account email address [address]

This is the email address from which system generated messages will come. Subscription confirmations, "Could not deliver" messages, various notification messages, and so on are all system messages.


Default attachment extension

System generated messages will be created using this extension. This will also be the extension assigned to attachments included with system generated messages. For example, if MDaemon generates a warning message to the postmaster about a specific message it will attach that message with an extension of ".md".


Default logon delimiter character (string of 10 characters max)

When using an email address as the account logon parameter, this character or string of characters can be used as an alternative to "@". This may be necessary for some users that have email clients which do not support "@" in the logon field. For example, if you used "$" in this field then users could login using "user@domain.com" or "user$domain.com".


CHAR-SET value for auto-generated messages

Specify the character set that you wish to be used for auto-generated messages. The default setting is US-ASCII.


Second machine IP for dual socket binding

If you want the Primary domain to be bound to an additional IP address then include it here.


Create "Everyone" mailing lists

Clear this checkbox if you do not wish "Everyone" mailing lists to be created and maintained for your domains. Maintaining mailing lists of every user on every MDaemon domain could be a potential waste of resources if the lists are never used or are for very large numbers of users. Clear this checkbox if you do not want MDaemon create these lists.


Deleting users via MDConfig also removes their mail directory

Click this checkbox if you want users’ mail directories to be deleted when their account is deleted via MDConfig. Otherwise, their account will be deleted but their messages and directories will remain.


"Subject" header for new account welcome messages

When MDaemon sends the "Welcome" message to new accounts, this text will appear as the message’s "Subject" header. The welcome message is constructed from the Welcome.dat file contained in the …/MDaemon/app/ directory, and this subject header control may contain any macros permitted in auto response scripts.


Enable disk space checking engine

Activate this checkbox if you want MDaemon to monitor the amount of disk space that is available on the drive where the MDAEMON.EXE is located.


Send warning to [user or address] when free disk space falls below [xx] KB

By using this option you can configure MDaemon to send a notification message to the user or address of your choice when disk space drops below a certain level.


MDaemon will automatically disable TCP/IP services if free disk space falls below [xx] KB

Enable this feature if you want MDaemon to disable TCP/IP Services if free disk space drops to a certain level.


Account list

Above the Account List you will see two statistics regarding the list. The first number is the total number of MDaemon user accounts that currently exist on your system. The second number is the number of those accounts currently displayed in the Account List. Which accounts that will be displayed is contingent upon what you have chosen in the Show Only Accounts From This Domain control. If you have selected “All Domains” then all of your MDaemon accounts will be displayed in the list.

Each Account List entry lists the Domain to which it belongs, the Mailbox, the “Real Name” of the account holder, and the Mail Directory in which the account’s messages are stored. This list can be sorted in ascending and descending order by whichever column that you prefer. Click any column heading to sort the list in ascending order by that column. Click the column again to sort it in descending order.

Note
By default, only 500 accounts at a time will be displayed in this list. If you want to see more accounts from the currently selected domain (or All Domains, if you have selected that option) then you must click the “Show More Accounts” button to display the next 500. If you want to be able to display more than 500 accounts at a time then open the MDaemon.ini file and change the MaxAccountManagerEntries=500 key to whatever value that you prefer.


Show only accounts from this domain

Choose “All Domains” from this drop-down list box to display all MDaemon accounts. Choose a specific domain to show only that domain’s accounts.


New

Click this button to open the Account Editor in order to create a new account.


Edit

Select an account from the Account List and then click this button to open it in the account editor.


Delete

Select an account from the Account List and then click this button to delete it. You will be asked to confirm you decision to delete the account before MDaemon will proceed.


Show more accounts

The account list will only display 500 accounts at a time. If there are more than 500 accounts in the domain that you have chosen then click this button to display the next 500. See the note above for instructions on how to increase the maximum number of accounts that may be displayed.


Top

Click this button to quickly move to the top of the Account List.


Import

This opens the OPEN dialog from which you can choose a text file to import accounts from. This button is identical to the Accounts|Import|From a text file… menu selection.


Mailbox

Use this field to specify a default Mailbox name template for new accounts. In addition to being the Mailbox, this value will be the name passed in the USER POP command, which enables access to a mailbox from a remote location or POP aware mail clients. See Template Macros for a list of the Macros that can be used in this template string.


Password

This template specifies a default POP Password for new accounts. This is the value passed in the PASS POP command, which allows access to a mailbox from a remote location or POP aware mail clients. See Template Macros for a list of the Macros that can be used in this template string.


Mail directory

Use this field to specify a default mail directory for new accounts. These directories are where the actual mail files delivered to the mailbox will be stored. Care must be taken to ensure that once expanded, the template provided here will form a true DOS™ path. See Template Macros for a list of the Macros that can be used in this template string.


Default account options

These switches are used for designating default values for various account settings. For more information on these switches, see Account Editor


Default quota options

These switches are used for designating default values for a new account’s quota settings.  For more information on these switches, see Account Editor


Template Macros

Below is a quick reference to the macros available for automating your account setup.

$DOMAIN$	This variable will resolve to the domain name selected for the account.
$DOMAINIP$	This variable will resolve to the IP associated with the domain currently selected for the account.
$USERNAME$	This variable resolves to the full first and last name of the account holder.  This field is equivalent to “$USERFIRSTNAME$ $USERLASTNAME$”
$USERFIRSTNAME$	This variable resolves to the first name of the account holder.
$USERLASTNAME$	This variable resolves to the last name of the account holder.
$USERFIRSTINITIAL$	This variable resolves to the first letter of the account holder’s first name.
$USERLASTINITIAL$	This variable resolves to the first letter of the account holder’s last name.
$MAILBOX$	This variable resolves to the mailbox name of the current account. The value will also used as the POP user name used in POP3 mail sessions.  This is the value expected in the USER command during POP session handshaking.


Apply installation defaults to all template values

Clicking this button will cause the controls contained on this tab to be reset to their original installation default settings.


Account can access email via WorldClient standard

Enable this checkbox if you would like new accounts to be able to access the WorldClient Standard server, which enables them to check their email using a web browser.


Accounts can modify Its own settings via  WebConfig

Enable this feature if you want to grant MDaemon users permission to modify their account settings via WebConfig. They will only be able to edit those settings that you designate on this dialog.

When this feature is enabled, and the WebConfig server is set to Active on the Message Router, users will be able to log on to WebConfig using their browser by pointing it to http://mdaemonsdomain.com:Port. They will first be presented with a logon screen and then a screen that contains the settings that they have been given permission to edit.  All they need to do is edit whatever settings they choose and then click the Save Changes button. They can then close their browser; there is no need to logoff or do anything further.

Accounts that have been given administrative permission (designated on the individual account’s Web tab) will see a different screen after they log on to WebConfig.

By default, accounts can do the following via WebConfig:


Edit real name

Enabling this feature will allow users to modify their Real Name setting.


Edit password

Click this checkbox if you wish to allow users to modify their POP Password.


Edit mail directory location

This control is used to give users permission to modify the location of their Message Directory.

Note
You should exercise caution in granting this permission to users. Giving users the ability to change their mail directory could effectively give them access to any directory on your system.


Edit forwarding address

When this feature is enabled users will be able to modify their forwarding address settings.


Edit advanced forwarding

When this feature is enabled users will be able to modify their Advanced Forwarding Options.


Edit encrypt mail setting

This feature allows users to control whether or not mail messages of 4096 bytes or less will be stored in their mailbox in an encrypted state.


Edit EVERYONE list setting

This feature allows users to control whether or not they will be included on MDaemon’s EVERYONE Mailing List.


Edit intranet only setting

Click this checkbox to restrict accounts to sending local mail only.


Edit quota settings

Click this checkbox if you wish to allow accounts to modify their quota settings.


Edit MultiPOP Settings

Click this switch if you wish users to be able to enable and disable MultiPOP collection.

Note
This permission doesn’t grant users the ability to create, delete, or edit MultiPOP entries in any way. MultiPOP entries must be created by the administrator using the MDaemon interface. This feature is for allowing users to control whether or not MultiPOP Mail Collection for their account is turned on.


Edit autoresponder settings

Click this checkbox if you want users to be able to add, edit, or delete AutoResponders for their account.


Edit allow changes via email

Click this checkbox if you wish to allow users to modify their Account Settings via specially formatted email messages.


Apply these defaults to all accounts now

Click this button to cause these default settings to be applied to all MDaemon accounts.  Any alternate settings that have been specified under individual accounts will be lost; the Web settings of all current MDaemon users will be changed to the settings specified here.


Edit IMAP rules (PRO version only)

Use this control to enable users to create and manage their own IMAP Mail Rules. This feature is only available in MDaemon PRO.


Real name

Enter the user’s first and last name here. When setting up a new mail account, the templates are reapplied each time the value in this field is changed. Real names cannot contain "!" or "|".


Mailbox name

This field specifies a unique name for the mailbox, and is also used as the account’s POP/IMAP login. In addition, the Mailbox must be unique and cannot contain spaces. After entering the name of the mailbox, click the drop-down list box and choose the domain to which this account’s mailbox will apply. MDaemon’s Primary Domain will appear in this control by default. Mailbox names cannot contain "!" or "|".


Allow this account to be accessed with POP/IMAP mail clients

This switch governs whether or not POP and IMAP access to the mailbox is allowed.


Account password

Enter an account password in this field. Below this field you will see a short statement that will tell you whether or not Dynamic NT Authentication is being used for this account.

Note
You should always provide Account Password information even if you do not wish to allow POP/IMAP access to the mail account. If you wish to disallow access then use the Allow This Account To Be Accessed… switch rather than leaving the Account Password field blank. In addition to POP session verification, user and password values are used to allow remote account manipulation and remote file retrieval.


Aliases

Click this button to open the Alias Editor, which will have the current account displayed and any aliases assigned to the account listed. You can use this dialog to edit previously configured aliases or create new ones.


Message directory

Enter the directory where inbound mail messages destined for this account’s mailbox should be placed.


Edit MBF

This button will allow easy editing of the account’s MBF file.


Storage format

This window allows you to attach an MBF to the mailbox message directory.  MBF files provide a method of mail system compatibility which may be useful in integrating your existing mail system with MDaemon Server v3.  For a complete discussion of MBF files and how to construct them see Creating and using MBF files .


Enable automatic extraction of MIME encoded attachments

If set, this switch causes MDaemon Server v3 to automatically extract any Base64  MIME embedded file attachments found within incoming mail messages.  Extracted files are removed from the incoming mail message, decoded, and placed in the account’s File Directory.  A notice is placed within the textual portion of the mail message in place of the encoded data which states where the file was placed and what the file name is.  This feature is extremely useful for mail transport systems and clients which do not have built in MIME capability or which require encoded parcels to be extracted and placed in separate directories from the textual portions of the mail message before being submitted into the mail stream.

User’s who wish to access their accounts through POP agents such as Eudora or the Windows Exchange client may wish this option to be turned off (not set) as more powerful email client software can properly handle MIME Base64 encoded attachments.


This account is currently forwarding mail

This switch governs whether or not mail will be forwarded to the address specified in the Forwarding Address field.


Forwarding address(es)

This field allows you to specify an address where copies of all inbound mail messages destined for this account will be automatically forwarded once they arrive at the server and are delivered to the account’s local mail directory.  A copy of each new message arriving at the server will be automatically generated and forwarded to the address specified in this field provided the This Account Is Currently Forwarding Mail switch is selected.


Retain a local copy of forwarded mail

If the account is forwarding mail to another address it may not be necessary for MDaemon to retain a copy of the message in the users local mailbox.  This switch governs that action.


Forward the message to this host

If a mail host is specified here the forwarded message will be delivered to it rather than to the domain specified by the value found in the Forwarding Address field.


Use this address in SMTP envelope

If an address is specified here, this address will be used in the SMTP “Mail From:” statement used during the session handshaking with the accepting host.  Normally, the sender of the message is used in this portion of the SMTP envelope. If you require an empty SMTP “Mail From:” command (looks like this: MAIL FROM <>) then enter “[trash]” into this control.


Use this TCP port

MDaemon will send this message on the TCP port specified here rather than the default SMTP outbound port.


Hide account from the 'EVERYONE' list, LDAP address book, and VRFY results

MDaemon automatically creates and maintains a mailing list called Everyone which can be used to address each account on the server. By default MDaemon will include all accounts when it constructs the Everyone mailing list. Uncheck this switch if you want the account to be private and hidden from other users. This will also hide the account from the LDAP address book and VRFY results.


Store mail messages in an encrypted state

If selected, MDaemon will store mail for this account in an encrypted state.  The messages will not be directly readable while in this state and should provide a very good level of protection.  MDaemon will decrypt the message when it is transmitted via POP to the account holder but while stored on disk this account’s message files will be encrypted.


Allow changes to account settings via email messages

This switch determines whether the user has access to account variables through remote email messages.  This feature allows the user to perform common account maintenance such as changing passwords or mail directories by sending specially formatted mail messages to the server.  For a complete discussion on remote account manipulation see Remote Server Control Via Email .


This account is restricted to sending and receiving local mail only

This switch may be used to limit an account so that it can only send local (Intranet) mail.  Local mail includes LAN and Gateway Domain mail as well.  A corresponding switch in the Account Template Editor lets you choose to set this as a default for creating new accounts if you so desire.


This account must observe these quota settings

Here you can specify the account’s maximum number of allowable messages and the maximum amount of disk space (in kilobytes) that the account can consume (this includes any decoded file attachments in the account’s File Directory). If a mail delivery to the account is attempted which would exceed the maximum messages limit or the maximum disk space allocated then the message is forwarded to the postmaster along with an appropriate warning. If a MultiPOP collection would exceed the account’s maximum a similar warning is issued and the account’s MultiPOP entries are automatically switched off (but not removed from the database).


Account can access email via WorldClient Standard

Enable this checkbox if you would the account to be able to access the WorldClient Standard server, which enables them to check their email using a web browser.


Account can modify its own settings via WebConfig

Enable this feature if you wish to grant the MDaemon user permission to modify their account settings via WebConfig.  They will only be able to edit those settings that you enable below.

When this feature is enabled, and the WebConfig server is set to Active on the Message Router, user will be able to log on to WebConfig using their browser by pointing it to http://mdaemonsdomain.com:Port.  They will first be presented with a logon screen and then a screen that contains the settings that they have been given permission to edit.  All they need to do is edit whatever settings they choose and then click the Save Changes button.  They can then close their browser; there is no need to logoff or do anything further.

If the user has been given administrative permission (by enabling This Account Can Edit Other Users And MDaemon Via The Web) they will see a different screen after they log on to WebConfig.

See WebConfig.


This account has administrator level access to WebConfig

Enable this checkbox to grant the user administrative access to WebConfig. This will give the user complete access to MDaemon’s files and options via the web.

See WebConfig.


Edit real name

Enabling this feature will allow the user to modify their Real Name setting.


Edit password

Click this checkbox if you wish to allow the user to modify their Account Password.


Edit mail directory location

This control is used to give the user permission to modify their Message Directory location.

• Caution!
You should exercise caution in granting this permission to users.  Giving users the ability to change their mail directory could effectively give them access to any directory on your system.


Edit forwarding address

When this feature is enabled, the user will be able to modify their forwarding address settings.


Edit advanced forwarding

When this feature is enabled, the user will be able to modify their Advanced Forwarding Options.


Edit encrypt mail setting

This feature allows the user to control whether or not mail messages of 4096 bytes or less will be stored in their mailbox in an encrypted state.


Edit IMAP rules (PRO version only)

Use this control to enable users to create and manage their own IMAP Mail Rules. This feature is only available in MDaemon PRO.


Edit EVERYONE list setting

This feature allows the user to control whether or not they will be included on MDaemon’s EVERYONE Mailing List.


Edit Intranet Only Setting

Click this checkbox to restrict the account to sending local mail only.


Edit quota settings

Click this checkbox if you wish to allow the account to modify their quota settings.


Edit MultiPOP settings

Click this switch if you wish the user to be able to enable and disable MultiPOP collection.

This control doesn’t grant the user the ability to create, delete, or edit MultiPOP entries in any way.  MultiPOP entries must be created by the administrator using the MDaemon interface.  This feature is for allowing users to control whether or not MultiPOP Mail Collection for their account is turned on.


Edit autoresponder settings

Click this checkbox if you want the user to be able to add, edit, or delete AutoResponders for their account.


Edit allow changes via email

Click this checkbox if you wish to allow the user to modify their Account Settings via specially formatted email messages.


Apply defaults

Click this button to cause the default settings designated on the Web Access Defaults dialog to be applied to this MDaemon account. Any alternate settings that have been specified on this individual’s account will be replaced by the Web Access Defaults settings.


Enable MultiPOP mail collection for this account

This switch must be enabled for MultiPOP processing to occur for the account.


Server

Enter the POP3 server from which you wish to collect mail.


Logon

Enter the POP3 USER or LOGON name that accesses the mail account on the specified server.


Password

Enter the POP3 password or APOP shared secret used for accessing the mail account on the specified server.


Use APOP (password field contains shared secret)

Click this checkbox is you want the MultiPOP entry to use the APOP method of authentication when retrieving mail from its corresponding host. Note: The Password control must contain the APOP shared secret when this feature is chosen.


Leave a copy of message on POP server

Click this checkbox if you want to leave a copy of collected messages on the server.  This is useful when you plan to retrieve these messages again at a later time from a different location.


Delete messages once [xx] or more have accumulated (0 = never)

This is the number of messages that MultiPOP will leave on the POP server before they will be deleted. When this number has accumulated, all stored messages will be deleted.  Enter "0" into this control if you do not wish to place a limit on the number of messages that may be stored.

Note
Some ISP’s limit the number of messages that may be stored so you should check with them about any restrictions that may apply to your account.


Don't download messages larger than [xx] KB (0 = no limit)

Enter a value here if you wish to limit the size of messages that may be downloaded.


Remove

Click this button to remove the selected MultiPOP entries from the list.


Enable/disable

Clicking this button toggles the state of the selected MultiPOP entries.  This switch gives you control over whether MDaemon will collect mail for this entry or skip over it when it performs its MultiPOP processing.


Add

Press this button to add your values to the list of MultiPOP records.


Replace

When an entry is selected from the list it will be presented for editing. After making any desired changes, click this button to apply them.


MultiPOP

The MultiPOP feature (located on the Account Editor) allows you to script an unlimited number of POP host/user/password combinations for collection of mail messages from multiple sources. This is useful for your users who have mail accounts on multiple servers but would prefer to collect and pool all their email together in one place. Before being placed in the user’s mailbox, MultiPOP collected mail is first placed in the local queue so that it can be processed like other mail having autoresponders and Content filters applied to it.

Note
This editor uses advanced common controls that were not present in the original shipping versions of Windows 95. If the MultiPOP editor will not retain your settings then you need to download and install the newer common controls DLL file from Microsoft (www.microsoft.com).


PDC/BDC Machine name

This field allows you to specify the machine name from which MDaemon will read NT account database information.  You can specify \\<DEFAULT> and MDaemon will read data from the local machine.


Refresh

Click this button to refresh the NT Accounts listing.


NT Domain Name

Type the NT domain name from which you wish to import accounts.


MDaemon Domain Name

Choose from the drop-down list box the MDaemon domain into which the accounts will be imported.


NT accounts

This window contains a list of all the account names collected from the NT account database.


Selected accounts

This window contains all the account names that you have selected and wish to import.


>>

Click this button to move the highlighted account names from the “NT Accounts” window into the “Selected Accounts” window.


<<

Click this button to remove the highlighted entries from the “Selected Accounts” window.


Use the account template to generate passwords

This switch causes MDaemon to generate passwords for imported accounts using the account template settings (see Account Defaults).


Set account passwords equal to account names

This switch causes MDaemon to use the account name as the account password.


Make Every Password Equal To
Make every password equal to…

This switch allows you to specify a static password value that will be used by all imported accounts.


Authenticate passwords dynamically using NT database

This switch enables dynamic authentication of imported accounts.  Rather than specifying a password MDaemon will simply authenticate the mail client supplied USER and PASS values using the NT database in real-time.


Authenticate on this NT domain

Enter the name of the Windows NT domain that MDaemon will use when authenticating connections dynamically. This is not the machine name of the domain controller. It is the actual name of the NT Domain.

Note
When accounts are configured for dynamic authentication on an NT machine the name of the NT domain preceded by two backslash characters is used in the account’s PASSWORD field and is stored unencrypted within the USERLIST.DAT file. For example, if an account is configured for dynamic authentication on an NT domain called ALTN the account’s password field will contain the value \\ALTN. The two backslash characters preceding the domain name trigger MDaemon that the password field actually contains the name of an NT domain and that MDaemon should attempt to authenticate the USER and PASS values provided by the mail client using that domain’s account database. It is an error for a password to start with two backslash characters unless it is configured for dynamic authentication as described above. In other words, you can’t just have regular passwords that start with two backslashes. Passwords beginning with two backslashes are always assumed to be providing an NT domain name and not a password. It is perfectly acceptable to enter two backslashes and the NT domain name into an account’s password field using the regular Account Editor if necessary. The administrator need not restrict himself to using the importer in order to setup accounts for dynamic authentication.


Make account mailboxes equal tothe NT account name

Click this switch to force each imported user’s NT account name to be used as their Mailbox value. With this method, you will not need to worry about setting up the correct New Account Template macros.


Address alias

Enter the email address for which you wish to create an alias. Wildcards of “?” and “*” are acceptable.


Actual address

Select an account from the drop-down list or type a new address or mailing list into this space. This is the actual address that will receive the message when it is addressed to a corresponding alias.


Add

Click the Add button to register the account alias request. The contents of the Address Alias and Actual Address fields will be combined and placed in the Current Aliases window.


It's OK to relay mail for aliases that include foreign domains

Click this control if you want MDaemon to relay mail for Address Aliases regardless of your Relay Control settings.


Aliases are ignored if address matches an existing account or mailing list


Up

Aliases are processed in the order in which they are listed. You can move an Alias to a higher position in the list by selecting it and then clicking this button.


Down

Aliases are processed in the order in which they are listed. You can move an Alias to a lower position in the list by selecting it and then clicking this button.


Remove

Click this button to remove a selected entry from the Current Aliases list.


Current aliases

This window contains all current Address Aliases that you have created.


Mailbox

This control lists all available local mailboxes that can host an Auto Responder. Select a mailbox from this drop-down list and then fill in the desired auto response parameters to cause the Auto Responder to be triggered whenever a message arrives for the mailbox.


Remove

Clicking this button will remove any Auto Responder that is associated with the account selected in the Mailbox drop-down list box.


Use this auto response script

This field specifies the full path and filename of the response file (*.RSP) that will be processed and dispatched to the message sender. This file will first be passed through the filtering mechanism associated with MBF files. Any template string available for use in an MBF file will also be available for use in an auto-response file.

See:

Creating Auto Response Scripts

Creating and Using MBF Files


Do not send auto response if message is from one of these addresses

Here you can list addresses that you wish to be excluded from responses initiated by this Auto Responder.

Note
Occasionally Auto Response messages may be sent to an address that returns an Auto Response of its own. This can create a "ping-pong" effect causing messages to be continually passed back and forth between the two servers.  You can use this feature to prevent an MDaemon Auto Responder from sending responses to one or more of these addresses by entering them here.


Del

Click this button to delete selected entries from the list of excluded addresses.


Add

After entering an address in the New Excluded Address text box, click this button to add it to the list of excluded address.


New excluded address

If you wish to add an address to the list of excluded addresses enter it here and then click the Add button.


Run this program

This field specifies the full path and filename to a program that will be launched when new mail arrives at the specified mailbox. Care must be taken to ensure that this process terminates properly and can run unattended. Optional command line parameters can be entered immediately following the executable path if desired.


Pass message to process

Select this option and the process specified in the Run This Process field will be passed the name of the triggering message as the first available command line parameter. Note that by the time the message name is passed to the specified process the account’s MBF file will already have been applied. This is useful in that applying an MBF can reformat the message into a consistent structure regardless of the source of the original message. When the auto responder is setup on an account which is forwarding mail to another location and not retaining a local copy in its own mailbox (see Forwarding) then this function will be disabled.

Note
By default, MDaemon will place the name of the message file as the last parameter on the command line.  You can override this behavior by using the $MESSAGE$ macro. Use this macro in place of where the message file name should be placed.  This allows more flexibility in the use of this feature since a complex command line such as this will be possible:  logmail /e /j /message=$MESSAGE$ /q


Add sender to this mailing list

If a mailing list is entered in this field then the sender of the mail message will be automatically joined to that mailing list. This is a very handy feature for building automatic lists.


Remove sender from this mailing list

If a mailing list is entered in this field then the sender of the mail message will be automatically removed from the specified mailing list.

TIP
Auto-Response events are always honored when the triggering message is from a remote source. For messages originating locally, whether or not an Auto Responder will but triggered is contingent upon a setting on the Miscellaneous Options dialog. The control is: Auto Responders are triggered by Local as well as Remote Traffic. Enable the control if you want Local mail to trigger an auto response.


Enable an auto responder for this account

Enable this control to activate an auto responder for the account. For more information on auto responders see: Auto Responders and MBF Files


Name

Specify a name for the mailing list and then choose the domain to which the list will belong form the drop-down list box. Messages directed to this list will use the name and domain specified here (e.g. mylist@mydomain.com). List names cannot contain "!" or "|".


List's "Reply-To:" address

Type the email address to which you want replies to this list to be directed.  Enter the list’s address if you want replies to be directed back to the it. You may enter an address other than the list name, or choose an address from the drop-down list if you want replies to this list to be directed to an alternate address. If you leave this field blank then replies to any list message will be directed back to the sender of that message.


This list is private and only members can send list traffic

When this control is enabled, the list will only propagate messages from list members.  Messages originating from non-members will be deleted.


This List Responds To EXPN and LISTS Requests
This list responds to EXPN and LIST requests

If this option is selected the membership of the list will be reported in response to an EXPN or LIST command during a mail session.  Otherwise, the list’s membership will be kept private.


Messages have list name in subject

This setting causes MDaemon to enclose the name of the list in brackets (e.g. [ListName]) and add it to the beginning of the Subject: in all messages sent to the list.


Messages have thread numbers in subject (ie. . . subject text {5} )

This switch allows you to toggle whether thread numbers will be displayed in the Subject: header of list messages. They are appended to the end of the subject line in braces and used as a pseudo-thread number. Sorting your inbox by subject will align list mail in chronological order.


Delivery precedence level for this list's traffic

Enter a number from 0-99 in this control. This value signifies the relative sort order of the messages during the delivery process. The lower the value, the higher its importance and the further up it will be in the sort order within a message queue.


Replace 'TO:' field with: N/A, list's name, member's full name

Use these options to designate what address will be displayed in the TO: field whenever MDaemon receives a message directed to the list.

N/A - When N/A is selected MDaemon will make no changes to the address displayed.  The address contained in the TO: field will appear exactly as the sender of the message entered it.

List’s Name - This option displays the address of the Mailing List in the TO: field.

Member’s Name - When this option is selected, the TO: field will contain the name of the list member to whom the message is directed.

Note
The Member’s Name option can only be chosen when "MDaemon Will Crack List Mail" has been selected on the Routing tab of the Mailing List Editor.  When "Route A Single Copy…" is selected, MDaemon will default to the List’s Name option.


Include "[listname] list member" in TO: field

When this feature is enabled, "[Listname] List Member" will be displayed in the "real name" portion of the message’s TO: field.

Note
Not all email clients support the displaying of "real names" in the TO: field of messages. In such clients only the actual email address designated in the "Replace TO: Field With…" feature will appear.


Don't distribute messages larger than XX bytes

This control places an upper limit on the size of a message accepted for this mailing list.  Messages larger than this limit are sent to the bad message directory.


Current member count:

This control displays the current number of users subscribed to the list and lists them in the box below. Each member’s entry also states his or her "type" of membership: normal, digest, read only, or post only.


Remove

This button removes the selected entries from the Current Members list.


Digest

Select a member and then click this button to make it a "Digest " membership.


Read only

Click this button after selecting a list member to give their membership "Read Only" status. They will still receive messages from the list but will not be allowed to send them to it.


Post only/no mail

Clicking this button after selecting a member will set their membership to "Post Only". They will be allowed to send messages to the list but will not receive any.


New member email

Enter the email address of the person you wish to add to the mailing list. Member’s addresses cannot contain "!" or "|".


New member real name

Enter the member’s name in this field. This name will appear in the "To:" field of their list messages when the "Replace ‘TO:’ field with: member’s full name" option is selected on the Options tab.


Normal, digest, read only, post only

Click the option that you want to be applied to the New Member’s Email Address.


Add

This button adds the entry in the New Member’s Email Address control to the Current Members list.


Default

Click any one of the options next to this button (Normal, Digest, Read Only, Post Only) and then click the button to make that option the default setting for new members.


Automatically remove dead addresses from list membership

When this feature is enabled, MDaemon will automatically remove an address from the Members list when it encounters a permanent fatal error while attempting delivery.  Addresses will also be considered "dead" and removed when their message is moved to the Retry system and subsequently expires from that system.


MDaemon will crack list mail

If selected, individual list messages will be created and dispatched to each list member.  This will result in numerous individual messages being created which could effect the server’s performance.  This option is appropriate for a mailing list of around 15 members or less.


Generate unique message id for each copy

When MDaemon cracks list mail it creates an individual copy of the message for each member.  If you wish MDaemon can make certain that each copy of the list message contains a unique identifier.


Route single copy of list mail to this smart host | host name

If selected, MDaemon will route a single copy of each list message to the specified smart host.  This method employs multiple RCPT TO commands during the SMTP session with the specified host.


Ignore errors when spooling list mail to host

Since some smart hosts will refuse to queue or spool mail for certain domains, the routed approach to list delivery could cause numerous problems.  An error code returned from the smart host as a result of this refusal would ordinarily cause MDaemon to abort the delivery attempt.  If this switch is set MDaemon will ignore error codes returned from the smart host during delivery of routed list mail thus allowing those members that are accepted a chance to receive the list message.


This host allows [XX] RCPT TO's per message (0=no limit)

Some hosts limit the number of RCPT TO statements that they will accept when you are attempting to route a single copy of a message through them. If you specify the limit in this control then MDaemon will work around it by creating additional copies of the message and dividing the list into smaller groups. Then it will deliver the message to those groups thus avoiding the need to exceed the limitation. This is similar to “cracking” the list, but into groups instead of individuals.


New member welcome file

If specified, the file listed here will be processed and mailed to all new members just after they subscribe. The file is processed and handled exactly the same way as Auto-Response scripts and may therefore contain any macro available to them.

See:

Creating Auto Response Scripts


Apply this suppression file

If specified, the file listed here will be used to suppress messages sent from specified users.


Apply this header/footer file

The contents of the files specified here will be used as the header and/or footer file for list messages.


Send a message to

This control lists an address that will be notified when the selected events take place.


When a user subscribes to this mailing list

If selected, a note will be sent to the address specified in the associated control each time someone subscribes to the mailing list.


When a user unsubscribes to this mailing list

If selected, a note will be sent to the address specified in the associated control each time someone unsubscribes to the mailing list.


When a message arrives which exceeds the max size limit

If selected, a note will be sent to the address specified in the associated control each time someone sends a message to the mailing list that is larger than the maximum acceptable size.  Such messages are moved into the bad message directory.


Notify non-members of message rejection (private lists only)

When non-members of a private list send mail to the list, MDaemon will inform them that the list is private.  They will also be given instructions on how to subscribe to lists.


Notify subscribers/unsubscribers on the status of their requests

When this checkbox is enabled MDaemon will send a completion notification message to the user that has been subscribed/unsubscribed to the Mailing List.


Send all mail returned to the list to

Here you specify who should receive any returned mail generated from list traffic. For example, a mailing list with 100 recipients will generally have 10-20 undeliverable addresses either due to address changes or down servers or whatever. The SMTP system will generate and return to the sender of the message notification mail concerning these undeliverable conditions. You can configure who should receive these messages for your mailing lists. You can also specify that no one should receive them in which case MDaemon will place list mail into the mail stream in such a way that return mail will not be possible.


This list  is moderated by

If set, the list will be moderated by the specified user.  Moderated lists forward all posts to the moderator.  The moderator alone may submit or forward messages to the list.


Anyone can post who knows the list's password

If this option is checked the moderator can assign a password to the mailing list.  Messages submitted to a moderated list that have the appropriate password specified as the first X characters of the subject line will not be subject to moderation - that is, the message will be immediately posted as if it had come from the moderator.

For example:  to bypass the moderator on a moderated list called MDSUPP, which has a password of ALTN, make ALTN the first 4 characters of the message subject.


Password

Enter the lists access password in this control.


Limit this list's membership to [xx] members (0=no Limit)

With this feature you can place an upper limit on the number of people who are allowed to subscribe to the Mailing List.  Enter a zero into this field if you do not wish to limit list subscriptions.

Note
This limit is only placed upon those who can Subscribe to the list through the Subscribe command.  This limit does not apply to subscriptions entered through the MDaemon interface, or through Subscription commands that are accompanied by the list Password.


Allow people to subscribe to this mailing list via email

This switch controls whether or not the list will allow potential members to subscribe to the mailing list by sending a subscription request to MDaemon.


Authenticate subscription requests

With this switch set MDaemon will attempt to authenticate the subscription request.  The mechanism employed to accomplish this consists of MDaemon generating a unique password string for the subscription transaction.  A message is sent to the potential member which contains this unique password.  Once the potential member responds by replying to this message MDaemon will then add the member to the mailing list’s membership.


Allow people to unsubscribe from this mailing list via email

This switch controls whether or not the list will allow members to quit the mailing list by sending an unsubscription request to MDaemon.

See:

Remote Server Control Via Email


Authenticate unsubscription requests

With this switch set MDaemon will attempt to authenticate the unsubscription request.  See Authenticate Subscription Requests above for a discussion of the mechanism employed to accomplish this.


Outstanding authentication requests expire after XX minutes

When someone is subscribed or unsubscribed, this is the amount of time that they have to confirm the subscription command before it will be discarded. MDaemon will generate a confirmation message and send it the subscribed address. The recipient must reply to the message within the designated time limit before the subscription command will be considered valid. This value is global; it applies to all MDaemon mailing lists not just the one that is currently being edited.


Authenticate auto-responder generated subscribers

Click this option if you want authentication to be required when the member is added via the Add Sender to This Mailing List Auto responder feature.


Authenticate auto-responder generated unsubscribers

Click this option if you want authentication to be required when the member is removed via the Remove Sender From This List Auto responder feature.


Enable digest support for this mailing list

This control determines whether this mailing list support message digests. When digest support is enabled a copy of each message sent to the mailing list will be archived. Members of the mailing list who have elected to receive traffic from this list in digest form will be sent these archived messages in a compact and easy to use indexed format.


Insert HTML shortcut links into digest messages

When this control is enabled, MDaemon will convert all URLs found within digest messages to hypertext links.


Force all members to use digest mode

By default, list members can control whether they wish to receive list traffic in digest or regular format. This control forces all members to use digest mode irrespective of the mode they may have chosen for themselves.


Storage format

Select the MBF file that individual messages placed into the digest will be conformed to. The default DIGEST.MBF file provides typical functionality comparable to most other mailing list software. For complete details on how to create MBF files see Creating and Using MBF Files.


Edit MBF

Click this button to edit the Mailbox Format file listed in the Storage format control.


Send Digest Mail At 9, 12, 3, 6  AM and/or PM

Mailing list digests must periodically be sent to those list members who are set to receive mail in digest format. These controls allow you to configure when you wish MDaemon to do this.


Spool digest mail if [XX] messages have accumulated (0 = N/A)

Sometimes digests should be sent to list members based upon the number of messages that have accumulated rather than (or in addition to) specific times. This control allows you to specify the number of messages that the list will accumulate before sending the digests to digest mode list members.


Spool digest mail if [XX] lines of message text received(0 = N/A)

This control will cause Digest mail to be sent immediately when a digest grows to this many lines of text.


Archive digests into a file catalog / which catalog do you want to use?

These controls allow you to place digest messages into a file catalog so that back-issues of the digests can be collected in the future. MDaemon will generate a unique archive name for each digest and place it into the catalog you specify.

For complete information on how to work with catalogs see:

Catalog Editor


Name

Use this field to enter a name for the file catalog.


Password

Use this field to enter a password for the file catalog.

Note
With MDaemon v3, a password is no longer required for all catalogs. You may choose to make catalogs accessible without a password.

See:

Mailing List and Catalog Control


File listing

This window displays all the files and their associated “magic names” currently registered as members of the specified catalog. Double click on an entry in this window to remove it from the catalog.


Remove

Click this button to remove a selected entry from the File Listing.


Add file

Click this button to add a file to the catalog. After choosing the file that you wish to add you will be prompted for the “Magic name” that you wish to assign.


Domain name

Enter the name of the domain for which you wish MDaemon to act as an email gateway.


Place message files for all users of this domain here

Enter the directory where you want to store incoming mail for the domain.


Automatically-Extract Embedded Attachments

Some mail systems require attached files be extracted before submission of mail messages to the mail stream. To facilitate this, MDaemon can auto-extract incoming MIME attachments and place them in the \Files\ subdirectory underneath the domain’s message directory. This directory will only be used if the "Auto-Extract" switch is selected.


Apply This MBF to Incoming Messages

The MBF file specified here will be applied to all incoming messages that arrive for the domain. This allows for any special reformatting that may be required.


Respond to ESMTP ETRN requests made for this domain

When this switch is enabled MDaemon will respond to ESMTP ETRN requests made by qualified hosts on behalf of the domain for which MDaemon is acting as an email gateway. The ETRN command is an SMTP extension that signals a server storing mail for a particular domain that it is time to begin spooling the mail. When MDaemon receives an ETRN request for a domain, it will immediately begin spooling the stored mail for delivery using subsequent SMTP transactions. Please note that the SMTP session that issues an ETRN request will not be the one that receives any stored mail. MDaemon will use subsequent independent SMTP transactions to send any mail it has stored for the domain. This preserves the message envelope and is more secure. Also note that the host to which MDaemon will spool any stored mail may not immediately begin reception of these messages. ETRN only guarantees that any stored mail is spooled for delivery. The actual process of delivery is subject to other administrator-imposed restrictions and may have to wait in the outbound mail queue for the next scheduled remote mail processing event to take place. Because of these limitations we recommend using On-Demand Mail Relay (ODMR) and its ATRN command rather than ETRN. This method is not supported by all clients and servers, however, and will therefore only be available to client domains using a server that does so. MDaemon fully supports ODMR on both the client and server side.


Spool all mail to this host

This is the host name or IP address to which any stored mail will be sent when an ETRN request is received and honored.  This machine must be running an SMTP server to receive these messages.


If the domain listed above is local treat it as if it were foreign

Activate this control if the domain is local but you want its mail to be spooled as if it is remote.


Spool all mail to IP of machine making ETRN request

Selecting this option will cause MDaemon to send any stored mail to the IP address of the machine that made the ETRN request. The requesting machine must be running an SMTP server to receive these messages.


Use this port when spooling mail

Use this control to specify the port on which the domain’s mail will be spooled.


Honor ETRN requests from these IP's

Select this switch and MDaemon will honor ETRN requests made from any IP listed in the associated address list.


Ignore ETRN requests from these IP's

Select this switch and MDaemon will ignore ETRN requests that are made from any IP listed in the associated address list.


Add new IP

To add a New IP to the current list simply enter the IP into this text box and click the ADD button.


Remove

Click this button to remove a selected entry from the list of IP addresses.

TIP
Although there is nowhere on this screen to enter it, you can control the SMTP envelope ID that MDaemon will use when spooling the domain’s mail. The following key controls this in the GATEWAYS.DAT file:

[GatewayDomainName]
EtrnAs=address@domain.com


Forward mail to this host

Sometimes it is advantageous to simply forward a copy of all messages for a domain as they arrive.  If you wish to configure MDaemon to do this then enter the name or IP address of the SMTP server to which copies of incoming mail for this domain should be sent.


Forward mail to this address

Use this feature if you wish to forward to a specific email address all email messages destined for this client domain.


Use this address in SMTP envelope

MDaemon will use this address in the SMTP "Mail From" transaction.


Forward mail using this TCP port

MDaemon will forward this mail using this TCP port.


Retain a local copy of all forwarded messages

Select this option if you wish MDaemon to retain a copy of a message locally once it has been forwarded.


POP access

Early versions of MDaemon pioneered a method of mail collection known as DomainPOP.  You can configure domains for which MDaemon is acting as an email gateway so that MDaemon will be their DomainPOP host. In other words, all the mail for the domain will be collected in a single mailbox on your server. With the controls on this tab you can create an account in your user list that will have access to these messages. This account can also be accessed using a regular POP client instead of an MDaemon, though in that case DomainPOP parsing would not be available.


Name

Enter the POP USER name that the client domain will use to access the messages stored in its mailbox.


Pass

Enter the POP PASS password that the client’s domain will use to access the messages stored in its mailbox.


Create/update account

Click here to create an account or to update the NAME and PASS values if the account already exists.

Note
You can completely edit (or even remove) an account using the Account Editor. Be careful if you remove an account because that will delete the account’s mail and file directories - which also happen to be the ones the gateway is using!


Automatically cache spam blocker results

Enable this control if you want to cache those IP addresses that receive a positive (i.e. blacklisted) result from a Spam Blocker lookup.

• Warning!
Although caching addresses may conserve some resources—since Spam Blocker lookups will not need to be performed on those IP addresses which have already been cached—it is not recommended by the Spam Blocker Hosts. Since a blacklisted IP address could have its status corrected in a matter of minutes, caching entries could result in mail being refused unnecessarily. Therefore, caution should be used when caching entries. If you choose to use this feature then we recommend keeping the amount of time small that any given entry will be cached. For more information on the implications of caching Spam Blocker lookups, see: www.mail-abuse.org.


IP address

Enter the IP address that you wish to manually add to the Spam Blocker cache.


Default time to live (in minutes)

This is the amount of time that the entry will remain in the Spam Blocker cache. Entering 9999 into this field will prevent the entry from expiring—however this is not recommended.


Maximum cached entries

This is the maximum number of entries that you want to allow to be cached.


Add

After entering the IP Address and Default Time To Live click this button to add the entry to the list of cached IP addresses.


Currently cached entries

This box list the IP addresses that are currently cached. MDaemon will not perform a lookup on them. They will be treated as blacklisted addresses.


Remove

Select an entry and then click this button to remove it from the list of cached addresses.


Clear

Click this button the clear the list of all cached IP addresses.


Network resource access

When running MDaemon as an NT/2000 system service, by default it runs under the LocalSystem account. Because this account does not have access to network devices, MDaemon will not be able to access mail if you wish to store it on other computers across your LAN. That is, not unless you provide logon credentials for an account that can be used to provide the MDaemon service access to network shares. We recommend creating a user account specifically designed for running MDaemon with whatever restrictions that you desire, but which has access to those network shares that you want MDaemon to be able to use. That way you can access network shares with UNC notation or mapped drives when running MDaemon as a service. Further, all applications launched by MDaemon (e.g. MDStats and Pre-Processing utilities) will also use the security context of this same NT Account.


Logon name

This is the logon name of the NT Account under which the MDaemon service should run.


Password

This is the NT Account’s password.


Domain

This is the NT Domain on which the account resides. Leave this field blank to logon to the default domain.


Allow WorldClient users to send faxes through RelayFax

Enable this control in order to integrate RelayFax with WorldClient. When active it will cause a “Compose Fax” control and other fax related features to appear on the WorldClient pages.


Use SMTP to deliver faxes to RelayFax

RelayFax monitors a specific mailbox for incoming messages that are to be faxed. Click this option and MDaemon will use the normal SMTP email delivery process to send these messages to that mailbox’s address. This option is useful when RelayFax is monitoring a mailbox located somewhere other than your LAN. If RelayFax resides on your LAN you may choose to have MDaemon deliver the messages directly to RelayFax’s message queue and thus bypass the SMTP delivery process altogether. For more information on this method, see Directly deliver faxes into RelayFax’s incoming queue below.


RelayFax server's email address

Specify the email address to which you want messages intended for faxing to be delivered. This value must match the address that you have configured RelayFax to monitor for these messages.


Directly deliver faxes into RelayFax's incoming queue

If RelayFax resides on your LAN you may choose this method rather than SMTP for distributing messages to it for faxing. When MDaemon receives a messages intended for RelayFax it will place it directly into RelayFax’s incoming queue rather than deliver it using SMTP. If RelayFax resides on the same machine on which MDaemon is running you may leave the file path field blank. Otherwise, you must specify the network path to RelayFax’s \app\ directory.


These IPs are on my local LAN

Like the LAN Domains tab, this tab is used to list IP addresses that reside on your LAN and thus do not require dialup in order to deliver messages to them. If a RAS session is in progress while messages are being delivered to these IP addresses and no non-local addresses remain, MDaemon will close the RAS session and continue to deliver the remaining Local IP messages.


Remove

Select an IP address from the list and then click this button to remove it. You may also double click an entry to remove it.


New local LAN IP

Enter an IP address to add to the local IP list and click Add. Wildcards like 127.0.*.* are permitted.


Add

After entering an IP Address into the New local LAN IP control, click this button to it to the list.


Enable an auto responder for this account


Dequeuing mail requires authentication

When you have configured the settings for this domain to accept ESMTP ETRN requests, you may use this tab’s controls to require the connecting host to first authenticate itself using the ESMTP AUTH command. Since ATRN requires authentication, this control must be enabled before MDaemon will respond to ATRN requests.


AUTH shared secret

Enter the client domain’s "Shared Secret" or password here that will be used during authentication.

Note:
The domain for which MDaemon is acting as a gateway must use its domain name as the logon parameter.


Authenticated requests are valid regardless of connecting IP

Enable this checkbox if you want to honor authenticated requests regardless of the IP address from which they are coming. If this control is not enabled then only requests from those IP addresses specified in the IP Access section of the ESMTP ETRN tab will be honored.


Respond to ESMTP ATRN commands for this domain (requires AUTH)

Activate this control if you want MDaemon to respond to ATRN commands from the domain for which MDaemon is acting as a gateway. ATRN is a new ESMTP command used in On-Demand Mail Relay (ODMR), which is currently the best relay method available for mail hosting. It is superior to ETRN and other methods in that in requires authentication before mail is dequeued and does not require a static IP address. A static IP address isn’t required because the flow of data between MDaemon and the client domain is immediately reversed and the messages are despooled without having to make a new connection—unlike ETRN, which uses a separate connection after the ETRN command is sent. This enables client domains using a dynamic (non-static) dialup account to collect their messages without having to use POP or DomainPOP to distribute them to their users because the original SMTP envelope is preserved.


Mirror account email addresses and full names to LDAP address book

Enable this control if you want MDaemon to keep your LDAP server up to date on all of your users’ names and email addresses.


Host name or IP

Enter the host name or IP address of your LDAP server here.


Port

Specify the port that your LDAP server is monitoring. MDaemon will use this port when posting account information to it.


Base entry DN

Enter the distinguished name of the base entry (root DN) that will be used in all of your MDaemon user entries.


RDN filter

The relative distinguished name (RDN) is the leftmost component in each entry’s distinguished name (DN). For all peer entries (those sharing a common immediate parent) the RDN must be unique, therefore we suggest using the email address of each user as their RDN to avoid possible conflicts. Using the $EMAIL$ macro as the value of the attribute that you specify in this control will cause it to be replaced by the user’s email address when their LDAP entry is created. The user’s DN will be comprised of the RDN plus the Base entry DN above.


Bind DN

Enter the DN of the entry to which you have granted administrative access to your LDAP server so that MDaemon can add and modify your MDaemon user entries. This is the DN used for authentication in the bind operation.


Bind Password

This password will be passed to your LDAP server along with the Bind DN value for authentication.


Object class

Specify the object class to which each MDaemon user’s entry must belong. Each entry will contain the objectclass= attribute with this as its value.


Configure

Click this button to open the LDAP.dat configuration file in a text editor. It is used for designating the LDAP attribute names that will correspond to each MDaemon account field.


Start SLAPD when MDaemon starts

Click this checkbox if you want to launch your LDAP server when MDaemon starts. At startup MDaemon will run the program specified in the SLAPD command line field.


SLAPD command line

If you want MDaemon to launch your LDAP server at startup then type its startup command line into this field.


Hide the SLAPD window

Click this checkbox if you want launched program’s window to be hidden.


Pause [xx] seconds to allow SLAPD to completely load

This is the number of seconds that MDaemon will pause its operations after launching the program specified in the command line. This pause is to give the program time to fully load before MDaemon begins processing messages.


This gateway must observe these quota settings

Here you can specify the domain’s maximum number of allowable messages and the maximum amount of disk space (in kilobytes) that it can consume. This includes any decoded file attachments in its Files directory.


Place a warning message in gateway mail directory when over quota

If this control is enabled and a mail delivery to the domain is attempted that would exceed the maximum message or disk space limitations, the message will be forwarded to the designated address along with an appropriate warning.


Address warning message to

Specify the address to whom the over quota warning message should be sent.


Address warning message from

Specify the address from whom the over quota warning message should appear to have been sent.


IMAP Mail Rules

New to MDaemon 3.5 is the ability for IMAP users to have their mail routed automatically to specific folders directly on the server. Similar to the Content Filters, MDaemon will examine the headers of each message and then compare them to rules. When a message for the account holder matches one of their rules, MDaemon will move it to the folder specified in that rule. This method is much more efficient (for both the client and server) than attempting to filter the messages at the client, and since some IMAP clients do not even support message rules or filtering, IMAP Mail Rules provides this functionality to them.

IMAP Mail rules and messages folders can be created directly on the server via the IMAP Mail Rules tab of the Account Editor. They can also be created by the users themselves via specially formatted email messages. Support for managing IMAP Mail Rules has also been added to WebConfig. By simply logging in to WebConfig with their browser they can manage their own account rules and settings that you have given them permission to manage. Thus, by using WebConfig you can give your users total control over their own rules and avoid having to manage those functions for them.


Existing IMAP Mail Rules

This box displays the list of all rules that have been created for the user’s account. Rules are processed in the order in which they are listed until a match is found. Therefore, as soon as a message matches one of the rules it will be moved to the folder specified in that rule and then rule processing for that message will cease. Use the Up and Down buttons to move rules to different positions in the list.


Remove

Click a rule in the list and then click Remove to delete it from the list.


Clear all

Clicking this button will delete all of the user’s IMAP Mail Rules.


Up

Click a rule in the list and then click this button to move it to a higher position in the list.


Down

Click a rule in the list and then click this button to move it to a lower position in the list.


If the [message header] header

Type a message header into this box or choose one from the drop-down list. MDaemon will search this header in all of the account’s incoming messages for the text contained in the "This text" control below. Then, based upon the type of comparison being made, it will determine which messages should be moved to the rule’s specified folder.


Is equal to, is not equal to, contains, doesn't contain

This is the type of comparison that will be made when a message’s headers are compared to this IMAP Mail Rule. MDaemon will search the specified header for the text contained in the "This text" field and then proceed based upon this control’s setting—does the header’s complete text match exactly, not match exactly, contain the text, or not contain it at all?


This text

Enter the text that you want MDaemon to search for when scanning the message header that you have specified for this rule.


Then move message to this folder

After specifying the various parameters for the rule, click the folder that you want messages matching it to be moved to and then click the Add rule button to create it.


New folder

Click this button to create a new folder. This will open the Create Folder dialog on which you will assign a name for the folder. If you want it to be a subfolder of an existing folder then choose the folder from the drop-down list.